Re: Purging the Page Table (was: Purging the Buffer Cache)

--- 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 > > invalidate_buff

Re: Purging the Page Table (was: Purging the Buffer Cache)

--- 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 invalidate_buffers() or destroy_buffers()? What about the ioctl

Purging the Buffer Cache

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

Purging the Buffer Cache

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

e2fs block to physical block translation

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!

e2fs block to physical block translation

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!

put/get_module_symbol vs. inter_module_register/put/get/etc.

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

put/get_module_symbol vs. inter_module_register/put/get/etc.

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

hard_sector / hard_nr_sectors

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

hard_sector / hard_nr_sectors

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

No Subject

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 Peat

No Subject

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 Peat

module reentrancy

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

module reentrancy

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