Anton Altaparmakov wrote:
> Hi, the below patch adds a new exported functon init_address_space() and
> two inline helpers to share code between it and inode_init_once() and
> This function allows file systems to initialize private address spaces
> without the need to know about the address space internals.
Looks good to me, Anton. Assuming it boots and runs and stuff ;)
Maybe sometime we should allocate the address_space separately
from the inode - may get better slab packing. But that's a
> Andrew, not sure what you have in mind for the future of ra_pages, so for
> now I am just passing in the super block to init_address_space. Is that
I'll test it a bit.
The "future of ra_pages" is worth discussion. We have all these
lovely abstraction layers in the kernel but unfortunately, the
real world sometimes comes up and whacks you in the head. The very
high-level code needs to know stuff about the very low-level device.
The case in point is the chosen device readahead. It lives in the
request queue, so it is device-wide, which is logical.
Also, the high-level code needs to know the answer to the question
"is there currently a pdflush thread writing to this device"? And
again, that is a device-wide thing which needs visibility at very
high levels. It's a waste of resources to have more than one
pdflush thread blocked against a request queue.
At present I have all this dopey code in there with superblock flags
and local flags and stuff which tries to prevent the kernel from
launching multiple pdflush threads against the same device. It doesn't
work very well. It needs a device-wide test-and-set flag in the request
So for this, `unsigned int ra_pages' will become `struct backing_device_info'
or somesuch. It will hold ra_pages and the pdflush exclusion flag.
One other thing which high-level code needs to know about the underlying
device is the nominal write bandwidth. If we know this then we can start
to make better writeback throttling decisions - avoid flooding the
machine with data which is dirty against really slow devices. That will
be a complex task, but struct backing_device_info is the place to keep that
So ra_pages is a damn great layering violation, one which we simply
have to have. The aim is to encapsulate that in as clean a way as
we can, in a way which is also useful to non-request_queue-backed
address_spaces. Such as NFS. At present, NFS shares default_ra_pages
with all other non-request_queue-backed address_spaces. But it could
define its own ra_pages (later backing_device_info) and make its
address_spaces point at that at inode init time.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 07 2002 - 22:00:23 EST