mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Switching TestSetPageLocked to trylock_page
Date: Tue, 5 Aug 2008 14:46:52 +1000	[thread overview]
Message-ID: <200808051446.52538.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <alpine.LFD.1.10.0808042106250.3299@nehalem.linux-foundation.org>

On Tuesday 05 August 2008 14:25, Linus Torvalds wrote:
> On Tue, 5 Aug 2008, Nick Piggin wrote:
> > The part that helps x86 is another patch further down my stack, which
> > can avoid looking at the hashed page waitqueue at unlock_page-time.
> > Basically this eliminates the entire page waitqueue from the cache
> > footprint of fastpath workloads where the lock is uncontended (often:
> > page faulting, write(2), writeout etc).
>
> Hmm. Tell me more. Contention bit?

Exactly. This is around the latest one online from a quick google:

http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/lock-bitops/2.6.22-rc4/mm-unlock-speedup.patch

      reply	other threads:[~2008-08-05  4:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  7:26 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
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 [this message]

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=200808051446.52538.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®