From: Andrea Arcangeli <andrea@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: nfs invalidates lose pte dirty bits
Date: Fri, 23 Dec 2005 03:36:03 +0100 [thread overview]
Message-ID: <20051223023603.GY9576@opteron.random> (raw)
In-Reply-To: <1135294250.3685.16.camel@lade.trondhjem.org>
On Thu, Dec 22, 2005 at 06:30:49PM -0500, Trond Myklebust wrote:
> See the latest git release where we introduce the nfs_sync_mapping()
> helper.
So you also still break completely with threaded programs, did you
consider that while fixing the most obvious problem? Isn't that a
problem too? What about my suggestion of invalidate_inode_clean_pages?
Still I wonder if messing with ptes for invalidates is worth it.
next prev parent reply other threads:[~2005-12-23 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 17:55 nfs invalidates lose pte dirty bits Andrea Arcangeli
2005-12-22 23:30 ` Trond Myklebust
2005-12-23 2:36 ` Andrea Arcangeli [this message]
2005-12-23 8:41 ` Trond Myklebust
2005-12-23 15:17 ` Andrea Arcangeli
2005-12-23 21:02 ` Trond Myklebust
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=20051223023603.GY9576@opteron.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox