From: Helge Hafting <helgehaf@aitel.hist.no>
To: Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, Joel.Becker@oracle.com
Subject: Re: statfs() / statvfs() syscall ballsup...
Date: Fri, 10 Oct 2003 22:33:45 +0200 [thread overview]
Message-ID: <20031010203345.GA1177@hh.idb.hist.no> (raw)
In-Reply-To: <20031010180535.GE29301@ca-server1.us.oracle.com>
On Fri, Oct 10, 2003 at 11:05:35AM -0700, Joel Becker wrote:
> The problem we have with msync() and friends is not 'quick
> population', it's "page is in the page cache already; another node
> writes to the storage; must mark page as !uptodate so as to force a
> re-read from disk". I can't find where sys_readahead() checks for
> uptodate, so perhaps calling sys_readahead() on a range always causes
> I/O. Correct me if I missed it.
>
Wouldn't this be solvable by giving userspace a way of invalidating
a range of mmapped pages? I.e. a "minvalidate();" to use when
the other node tells you it is about to write?
This will cause the pages to be paged in again on next reference,
or you can issue a read in advance if you believe you'll need them.
Helge Hafting
next prev parent reply other threads:[~2003-10-10 20:24 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 22:16 Trond Myklebust
2003-10-09 22:26 ` Linus Torvalds
2003-10-09 23:19 ` Ulrich Drepper
2003-10-10 0:22 ` viro
2003-10-10 4:49 ` Jamie Lokier
2003-10-10 5:26 ` Trond Myklebust
2003-10-10 12:37 ` Jamie Lokier
2003-10-10 13:46 ` Trond Myklebust
2003-10-10 14:35 ` Jamie Lokier
2003-10-10 15:32 ` Misc NFSv4 (was Re: statfs() / statvfs() syscall ballsup...) Trond Myklebust
2003-10-10 15:53 ` Jamie Lokier
2003-10-10 16:07 ` Trond Myklebust
2003-10-10 15:55 ` Michael Shuey
2003-10-10 16:20 ` Trond Myklebust
2003-10-10 16:45 ` J. Bruce Fields
2003-10-10 14:39 ` statfs() / statvfs() syscall ballsup Jamie Lokier
2003-10-09 23:31 ` Trond Myklebust
2003-10-10 12:27 ` Joel Becker
2003-10-10 14:59 ` Linus Torvalds
2003-10-10 15:27 ` Joel Becker
2003-10-10 16:00 ` Linus Torvalds
2003-10-10 16:26 ` Joel Becker
2003-10-10 16:50 ` Linus Torvalds
2003-10-10 17:33 ` Joel Becker
2003-10-10 17:51 ` Linus Torvalds
2003-10-10 18:13 ` Joel Becker
2003-10-10 16:27 ` Valdis.Kletnieks
2003-10-10 16:33 ` Chris Friesen
2003-10-10 17:04 ` Linus Torvalds
2003-10-10 17:07 ` Linus Torvalds
2003-10-10 17:21 ` Joel Becker
2003-10-10 16:01 ` Jamie Lokier
2003-10-10 16:33 ` Joel Becker
2003-10-10 16:58 ` Chris Friesen
2003-10-10 17:05 ` Trond Myklebust
2003-10-10 17:20 ` Joel Becker
2003-10-10 17:33 ` Chris Friesen
2003-10-10 17:40 ` Linus Torvalds
2003-10-10 17:54 ` Trond Myklebust
2003-10-10 18:05 ` Linus Torvalds
2003-10-10 20:40 ` Trond Myklebust
2003-10-10 21:09 ` Linus Torvalds
2003-10-10 22:17 ` Trond Myklebust
2003-10-11 2:53 ` Andrew Morton
2003-10-11 3:47 ` Trond Myklebust
2003-10-10 18:05 ` Joel Becker
2003-10-10 18:31 ` Andrea Arcangeli
2003-10-10 20:33 ` Helge Hafting [this message]
2003-10-10 20:07 ` Jamie Lokier
2003-10-12 15:31 ` Greg Stark
2003-10-12 16:13 ` Linus Torvalds
2003-10-12 22:09 ` Greg Stark
2003-10-13 8:45 ` Helge Hafting
2003-10-15 13:25 ` Ingo Oeser
2003-10-15 15:03 ` Greg Stark
2003-10-15 18:37 ` Helge Hafting
2003-10-16 10:29 ` Ingo Oeser
2003-10-16 14:02 ` Greg Stark
2003-10-21 11:47 ` Ingo Oeser
2003-10-10 18:20 ` Andrea Arcangeli
2003-10-10 18:36 ` Linus Torvalds
2003-10-10 19:03 ` Andrea Arcangeli
2003-10-09 23:16 ` Andreas Dilger
2003-10-09 23:24 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031010203345.GA1177@hh.idb.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=Joel.Becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--subject='Re: statfs() / statvfs() syscall ballsup...' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.