All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: David Kearster <david.kearster@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [rfc] lockless pagecache
Date: Tue, 28 Jun 2005 22:20:43 +1000	[thread overview]
Message-ID: <42C1409B.8000305@yahoo.com.au> (raw)
In-Reply-To: <3bba6cc4050628045676c61112@mail.gmail.com>

David Kearster wrote:
> Hi nick,
> 
> The patches that u posted on lkml regarding the vfs scalibility, on
> which kernel did u build them.
> I tried applying them on 2.6.12-git4, 2.6.12-mm1, mm2, 2.6.12.1, but
> to no avail.
> 

Hi David,

They are against 2.6.12-git4 plus a later revision of the PageRemoval
patchset I posted to linux-mm earlier, which is needed to make page
refcounting consistent.

I have a couple of updates and fixes for both sets of patches, so I
can send you a rollup of the current patches against a current -git
kernel privately if you would like.

Thanks,
Nick

-- 
SUSE Labs, Novell Inc.

Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2005-06-28 12:20 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 11:56 [rfc] lockless pagecache David Kearster
2005-06-28 12:20 ` Nick Piggin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-27  6:29 Nick Piggin
2005-06-27  6:29 ` Nick Piggin
2005-06-27  7:46 ` Andrew Morton
2005-06-27  7:46   ` Andrew Morton
2005-06-27  8:02   ` Nick Piggin
2005-06-27  8:02     ` Nick Piggin
2005-06-27  8:15     ` Andrew Morton
2005-06-27  8:15       ` Andrew Morton
2005-06-27  8:28       ` Nick Piggin
2005-06-27  8:28         ` Nick Piggin
2005-06-27  8:56     ` Lincoln Dale
2005-06-27  8:56       ` Lincoln Dale
2005-06-27  9:04       ` Nick Piggin
2005-06-27  9:04         ` Nick Piggin
2005-06-27 18:14         ` Chen, Kenneth W
2005-06-27 18:14           ` Chen, Kenneth W
2005-06-27 18:50           ` Badari Pulavarty
2005-06-27 18:50             ` Badari Pulavarty
2005-06-27 19:05             ` Chen, Kenneth W
2005-06-27 19:05               ` Chen, Kenneth W
2005-06-27 19:22               ` Christoph Lameter
2005-06-27 19:22                 ` Christoph Lameter
2005-06-27 19:42                 ` Chen, Kenneth W
2005-06-27 19:42                   ` Chen, Kenneth W
2005-07-05 15:11                   ` Sonny Rao
2005-07-05 15:11                     ` Sonny Rao
2005-07-05 15:31                     ` Martin J. Bligh
2005-07-05 15:31                       ` Martin J. Bligh
2005-07-05 15:37                       ` Sonny Rao
2005-07-05 15:37                         ` Sonny Rao
2005-06-27 13:17     ` Benjamin LaHaise
2005-06-27 13:17       ` Benjamin LaHaise
2005-06-28  0:32       ` Nick Piggin
2005-06-28  0:32         ` Nick Piggin
2005-06-28  1:26         ` William Lee Irwin III
2005-06-28  1:26           ` William Lee Irwin III
2005-06-27 14:08   ` Martin J. Bligh
2005-06-27 14:08     ` Martin J. Bligh
2005-06-27 17:49   ` Christoph Lameter
2005-06-27 17:49     ` Christoph Lameter
2005-06-29 10:49 ` Hirokazu Takahashi
2005-06-29 10:49   ` Hirokazu Takahashi
2005-06-29 11:38   ` Nick Piggin
2005-06-29 11:38     ` Nick Piggin
2005-06-30  3:32     ` Hirokazu Takahashi
2005-06-30  3:32       ` Hirokazu Takahashi

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=42C1409B.8000305@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=david.kearster@gmail.com \
    --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 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.