Operating Systems 2015F Lecture 7: Difference between revisions

From Soma-notes
 
(One intermediate revision by the same user not shown)
Line 4: Line 4:


==Notes==
==Notes==
===The project===
* Modify the linux kernel
* Document what you did and explain why you did it
* Evaluate what you did
You will submit:
* code
* a report
Suggested scope: make a "feedback loop"
* measure something
* change something
Don't limit yoursef to doing things that are "useful"
Entertaining is also good
Educational is also good
Feedback loops give systems personality
Go with it
Constraint: the system should still be "usable"
(But it may be annoying to use)
Hard part
* debugging can get weird
Groups are allowed
* but contribution of every group member should be clear, significant, and documented
Treat the "oral" portion (interview) as a proposal
Project should be "appropriate" for kernel implementation.
Project may include a userspace portion however.
===kernel source code===


During the lecture we looked a lot at the The Linux kernel cross reference, http://lxr.free-electrons.com/ .  Here are some of the pages that we looked at:
During the lecture we looked a lot at the The Linux kernel cross reference, http://lxr.free-electrons.com/ .  Here are some of the pages that we looked at:


* [http://lxr.free-electrons.com/source/kernel/sys.c?v=3.19#L822 getpid system call implementation]
* [http://lxr.free-electrons.com/source/kernel/sys.c?v=3.19#L822 getpid system call implementation]
* [http://lxr.free-electrons.com/source/include/linux/sched.h?v=3.10#L1034 struct task_struct]
* [http://lxr.free-electrons.com/source/include/linux/sched.h?v=3.19#L1274 struct task_struct]
* [http://lxr.free-electrons.com/source/fs/read_write.c?v=3.10#L333 do_sync_read()]
* [http://lxr.free-electrons.com/source/fs/read_write.c?v=3.19#L375 do_sync_read()]
* [http://lxr.free-electrons.com/source/include/linux/fs.h?v=3.10#L1517 struct file_operations]
* [http://lxr.free-electrons.com/source/include/linux/fs.h?v=3.19#L1507 struct file_operations]

Latest revision as of 14:45, 1 October 2015

Video

The video from the lecture given on September 30, 2015 is now available.

Notes

The project

  • Modify the linux kernel
  • Document what you did and explain why you did it
  • Evaluate what you did

You will submit:

  • code
  • a report

Suggested scope: make a "feedback loop"

  • measure something
  • change something

Don't limit yoursef to doing things that are "useful"

Entertaining is also good Educational is also good

Feedback loops give systems personality Go with it

Constraint: the system should still be "usable" (But it may be annoying to use)

Hard part

  • debugging can get weird

Groups are allowed

  • but contribution of every group member should be clear, significant, and documented

Treat the "oral" portion (interview) as a proposal

Project should be "appropriate" for kernel implementation.

Project may include a userspace portion however.


kernel source code

During the lecture we looked a lot at the The Linux kernel cross reference, http://lxr.free-electrons.com/ . Here are some of the pages that we looked at: