[lkml]   [1999]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: clustering page-ins
Chuck Lever wrote:
> true. but i'm also worried about sharing the read-ahead information
> amongst all mappers of a shared file. this case has come up in my
> benchmarking (although i haven't tracked it down, it is occurring in some
> basic commands that are run by the benchmark).

Since each mapping has its own vm_area, I don't see the problem.
Do you want different mappers to share read-ahead info?

> so, i think the information needs to be in the file struct so that shared
> maps don't continue to read ahead a file that is already in the page
> cache.

Sorry I don't quite understand what you want here. If you want to share
read-ahead info between different mappers, struct file isn't going to do
it -- each new open() creates a new struct file. If you don't, vm_area
and struct file won't make much difference.

It's only when you consider multiple mappings made from the same file
descriptor (or passed through fork/exec) that there's a difference: then
struct file leads to sharing while vm_area does not. There's also the
matter of files mapped and read with read() (e.g. ELF executables).

-- Jamie

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:53    [W:0.045 / U:28.384 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site