From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Switching TestSetPageLocked to trylock_page
Date: Mon, 4 Aug 2008 20:28:17 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808042024480.3299@nehalem.linux-foundation.org> (raw)
In-Reply-To: <200808051314.33791.nickpiggin@yahoo.com.au>
On Tue, 5 Aug 2008, Nick Piggin wrote:
> On Thursday 31 July 2008 17:26, Nick Piggin wrote:
> > Hi,
> >
> > I'm wondering if I could get a patch merged which changes all
> > TestSetPageLocked and replaces them with trylock_page?
>
> Yes? No?
>
> The alternative is try to merge it via -mm or -next, but that just
> wastes everybodies time with conflicts of having these differences
> between -mm and mainline.
Heh. I had just been _assuming_ this would go through -mm, since it's
exactly the kind of thing that usually does go through there.
So I hadn't even really considered it.
I don't mind the patch per se, but can you give some background on what
the pending optimization is that makes such a big difference?
Linus
next prev parent reply other threads:[~2008-08-05 3:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 7:26 Switching TestSetPageLocked to trylock_page Nick Piggin
2008-07-31 7:38 ` KOSAKI Motohiro
2008-07-31 9:33 ` Peter Zijlstra
2008-08-05 3:14 ` Nick Piggin
2008-08-05 3:28 ` Linus Torvalds [this message]
2008-08-05 3:41 ` Nick Piggin
2008-08-05 3:57 ` Andrew Morton
2008-08-05 4:01 ` Benjamin Herrenschmidt
2008-08-05 4:18 ` Nick Piggin
2008-08-05 4:09 ` Nick Piggin
2008-08-05 4:32 ` Linus Torvalds
2008-08-05 4:44 ` Nick Piggin
2008-08-05 4:57 ` Linus Torvalds
2008-08-05 5:09 ` Nick Piggin
2008-08-05 4:25 ` Linus Torvalds
2008-08-05 4:46 ` Nick Piggin
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=alpine.LFD.1.10.0808042024480.3299@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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 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.