Reply With QuoteHi,
What articles have you already found by searching Google and the Linux Kernel Mailing list?
Hi guys...my first post here, so please help out.....
I am a BSc student, and have recently started learning the basic of how OS's work, in my OS Concepts lectures....
I have recieved an assignment, in which I have to generally discuss the methods taken by the Linux OS, to resolves deadlocks in a multi-user environment....
I just need a brief article on this topic....
if anyone can help me out, I will be very grateful...
thanx in advance
Hi,
What articles have you already found by searching Google and the Linux Kernel Mailing list?
My crime is that of curiosity. My crime is that of judging people by what they say and think, not what they look like. My crime is that of outsmarting you, something that you will never forgive.
Originally Posted by trickster
well, i dont know about the Linux Kernel mailing list, but I have tried searching google, and I cant find anything there...
for LKML: http://www.kerneltrap.org/, perhaps this thread would be of interest.
As for google, wouldn't this search be a way to start ??
Atleast the first 10 results seems to be related with linux and deadlock handling...
Don't worry Ma'am. We're university students, - We know what We're doing.
'Ruiat coelum, fiat voluntas tua.'Datalogi - en livsstil; Intet liv, ingen stil.
hmmm..... the results have the word 'deadlock' in them, but they are no where near what i am looking for....
i dont want to rewrite a kernel....i have to write a paper on the schemes linux uses in general, to handle deadlocks in a multi user environment...
None of those comes to mind ??/usr/src/kernel/linux-2.6.16.19/Documentation> find . |grep -i lock
./DocBook/kernel-locking.tmpl
./block
./block/as-iosched.txt
./block/barrier.txt
./block/biodoc.txt
./block/deadline-iosched.txt
./block/ioprio.txt
./block/request.txt
./block/stat.txt
./filesystems/Locking
./filesystems/dentry-locking.txt
./filesystems/directory-locking
./fujitsu/frv/clock.txt
./infiniband/core_locking.txt
./locks.txt
./preempt-locking.txt
./spinlocks.txt
./vm/locking
From my point of view the spinlocks.txt, preempt-locking.txt, core_locking.txt, block/deadline-iosched.txt and DocBook/kernel-locking.tmpl seems to be related, it's all pressent in the kernel source documentation.. Which was exactly what myIs telling the person who's asking to look for.for LKML: http://www.kerneltrap.org/, perhaps this thread would be of interest.
A small quote from DockBook/kernel-locking.tmpl:
"Race Conditions and Critical Regions
This overlap, where the result depends on the relative timing of multiple tasks, is called a race condition.
The piece of code containing the concurrency issue is called a critical region. And especially since Linux starting running on SMP machines, they became one of the major issues in kernel design and implementation.
Which in my mind sounds an awfull lot like the scenario you would have in a deadlock situation.
Last edited by redhead; 06-13-2006 at 04:02 PM.
Don't worry Ma'am. We're university students, - We know what We're doing.
'Ruiat coelum, fiat voluntas tua.'Datalogi - en livsstil; Intet liv, ingen stil.
OK, fortunately, I have found a significant amount of data...when I google for 'Distributed Deadlocks'....this is good for me in the way that 'Distributed' I think means 'multi-user' in my question ....
the only problem is, in all the data i have gathered so far regarding distributed deadlocks, nothing mentions any particular OS that uses the methods described...
so, does linux have any distributed deadlock handling schemes ?
Posting Permissions
Bookmarks