From: Hugh Dickins <hugh@veritas.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: Page fault scalability patch V18: Drop first acquisition of ptl
Date: Fri, 04 Mar 2005 19:08:30 +0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0503041850170.24212@goblin.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503041004020.18056@schroedinger.engr.sgi.com>
On Fri, 4 Mar 2005, Christoph Lameter wrote:
> On Fri, 4 Mar 2005, Hugh Dickins wrote:
> > Nacked for the same reason as just given to earlier version. Ugly too.
>
> Ok. Then we could still get back the also ugly solution in the earlier
> patchsets that acquired the spinlock separately before getting to
> do_wp_page (also no need for the separate patch anymore). Patch is
> then shorter too.
Maybe. I should make it clear that I simply haven't examined the
recent incarnations of your patch, was just commenting on an issue
I could comment on quickly without needing to find time to think.
So, I just want to make clear, this absence of Nack doesn't mean
Ack: I remain uneasy with it all, waiting to see some architecture
maintainers come along with a clear "Yes, this is how it should be".
Hugh
next prev parent reply other threads:[~2005-03-04 19:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 3:49 Page fault scalability patch V18: Overview Christoph Lameter
2005-03-02 3:50 ` Page fault scalability patch V18: atomic pte ops, pte_cmpxchg Christoph Lameter
2005-03-02 3:51 ` Page fault scalability patch V18: abstract rss counter ops Christoph Lameter
2005-03-02 3:51 ` Page fault scalability patch V18: Drop first acquisition of ptl Christoph Lameter
2005-03-03 1:45 ` Andrew Morton
2005-03-03 2:13 ` Christoph Lameter
2005-03-03 2:55 ` Andrew Morton
2005-03-03 3:17 ` Christoph Lameter
2005-03-03 4:14 ` Andrew Morton
2005-03-03 4:27 ` Christoph Lameter
2005-03-03 4:56 ` Andrew Morton
2005-03-03 5:17 ` Christoph Lameter
2005-03-03 5:37 ` Andrew Morton
2005-03-03 5:48 ` Christoph Lameter
2005-03-03 6:13 ` Christoph Lameter
2005-03-03 6:20 ` Andrew Morton
2005-03-03 16:54 ` Christoph Lameter
2005-03-03 21:20 ` Andrew Morton
2005-03-03 22:14 ` Christoph Lameter
2005-03-04 16:44 ` Christoph Lameter
2005-03-04 17:09 ` Hugh Dickins
2005-03-04 18:29 ` Christoph Lameter
2005-03-04 19:08 ` Hugh Dickins [this message]
2005-03-31 6:55 ` Avoid spurious page faults by avoiding pte_clear -> set pte Christoph Lameter
2005-03-04 16:46 ` Page fault scalability patch V18: Drop first acquisition of ptl Christoph Lameter
2005-03-03 5:00 ` Paul Mackerras
2005-03-03 5:19 ` Christoph Lameter
2005-03-03 5:38 ` David S. Miller
2005-03-03 5:51 ` Christoph Lameter
2005-03-03 6:11 ` Benjamin Herrenschmidt
2005-03-03 16:52 ` Christoph Lameter
2005-03-03 5:54 ` Benjamin Herrenschmidt
2005-03-03 6:37 ` Nick Piggin
2005-03-03 6:30 ` Benjamin Herrenschmidt
2005-03-03 7:44 ` Nick Piggin
2005-03-03 17:43 ` David S. Miller
2005-03-03 5:24 ` Nick Piggin
2005-03-02 3:52 ` Page fault scalability patch V18: No page table lock in do_anonymous_page Christoph Lameter
2005-03-04 2:18 ` Page fault scalability patch V18: Overview Darren Williams
2005-03-04 2:47 ` Darren Williams
2005-03-04 16:15 ` Christoph Lameter
2005-03-06 21:49 ` Darren Williams
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=Pine.LNX.4.61.0503041850170.24212@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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