From: Arjan van de Ven <arjanv@redhat.com>
To: paulmck@us.ibm.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: Always passing mm and vma down (was: [RFC][PATCH] Convert do_no_page() to a hook to avoid DFS race)
Date: 02 Jun 2003 10:32:50 +0200 [thread overview]
Message-ID: <1054542770.5187.1.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030601200056.GA1471@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Sun, 2003-06-01 at 22:00, Paul E. McKenney wrote:
> The immediate motivation is to avoid the race with zap_page_range()
> when another node writes to the corresponding portion of the file,
> similar to the situation with vmtruncate(). The thought was to
> leverage locking within the distributed filesystem, but if the
> race is solved locally, then, as you say, perhaps this is not
> necessary.
is said distributed filesystem open source by chance ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-02 8:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 23:41 [RFC][PATCH] Convert do_no_page() to a hook to avoid DFS race Paul E. McKenney
2003-05-31 1:00 ` Andrew Morton
2003-05-31 23:51 ` Paul E. McKenney
2003-08-09 18:50 ` Christoph Hellwig
2003-08-10 12:06 ` Paul E. McKenney
2003-06-01 19:33 ` Paul E. McKenney
2003-05-31 8:46 ` Always passing mm and vma down (was: [RFC][PATCH] Convert do_no_page() to a hook to avoid DFS race) Ingo Oeser
2003-05-31 23:48 ` Paul E. McKenney
2003-06-01 12:22 ` Andrea Arcangeli
2003-06-01 20:00 ` Paul E. McKenney
2003-06-02 8:32 ` Arjan van de Ven [this message]
2003-06-02 13:13 ` Paul E. McKenney
2003-06-04 10:38 ` Andrea Arcangeli
2003-06-07 16:29 ` Paul E. McKenney
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=1054542770.5187.1.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@us.ibm.com \
/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