Re: Noob Query : About RAM Disks
- From: "David Schwartz" <davids@xxxxxxxxxxxxx>
- Date: 13 Oct 2006 12:20:57 -0700
Draw wrote:
I have been reading up about RAM Disks, but I don't seem to understand
how interrupts are generated for these.
They aren't. You only need an interrupt when a hardware operation might
complete or begin at an arbtirary future point in time.
I mean, considering block
io(maybe I am wrong in this assumption), given a situation that the
IO(writing specifically) is done, how does, lets say the FS routines,
know of that completion? Who sends them the interrupt?
The writing routines know of the completion because they complete. It's
not like a disk where the writing routines tell the disk to do the
write and the disk finishes (or accepts) the request later. As soon as
they finish doing the write, they're done. There's nothing to notify
them of.
If for some reason the write is done by another thread or "in the
background", the code that completes the write can signal other code
using a mechanism that has the same effect as an interrupt. But I don't
see why this would be necessary because there's really no reason to
wait for the write to complete.
DS
.
- References:
- Noob Query : About RAM Disks
- From: Draw
- Noob Query : About RAM Disks
- Prev by Date: Re: Nobody should ever need to patch the kernel!!
- Next by Date: Re: Open and Read functions
- Previous by thread: Noob Query : About RAM Disks
- Next by thread: Re: Noob Query : About RAM Disks
- Index(es):
Relevant Pages
|
