--- Juri Haberland <[EMAIL PROTECTED]>
wrote:
> Al Peat wrote:
> >
> > Is there any way to completely purge the buffer
> > cache -- not just the write requests (ala 'sync'
> or
> > 'update'), but the whole thing? Can I just call
>
Is there any way to completely purge the buffer
cache -- not just the write requests (ala 'sync' or
'update'), but the whole thing? Can I just call
invalidate_buffers() or destroy_buffers()?
I know, why in the world would a person do such a
thing? Research. It'd be easier for me to write a
Quick question about blocks:
If I assume my hard drive uses 512 blocks, and my
ext2 filesystem uses 4k blocks, can I assume the
following formula for translation?
physical block # / 8 = e2fs block #
Thanks,
Al
__
Do You Yahoo!?
Yahoo! S
I've followed the thread on "Persistent module
storage" but haven't come across a general explanation
of the changes to the inter-module symbol stuff
between 2.4test10 and test11. Anyone care to comment
on the differences or on whether this is going to be a
stable API for 2.4 (it won't be chang
I was wondering if someone could give me a quick
overview of the differences between sector/nr_sectors
and hard_sector/hard_nr_sectors in blk_dev.h's request
structure, or point me to some
documentation/discussion on this?
Thanks in advance,
Al
_
I was wondering if someone could give me a quick
overview of the differences between sector/nr_sectors
and hard_sector/hard_nr_sectors in blk_dev.h's request
structure, or point me to some
documentation/discussion on this?
Thanks in advance,
Al
I could use a little advice on reentrancy issues for
modules.
I have written a device driver that is nothing more
than a circular FIFO buffer in memory. The read and
write methods access user space, so I know that those
sections of code need to be reentrant. Since the
module represents one
7 matches
Mail list logo