From: David Kearster <david.kearster@gmail.com>
To: nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: RE: [rfc] lockless pagecache
Date: Tue, 28 Jun 2005 17:26:10 +0530 [thread overview]
Message-ID: <3bba6cc4050628045676c61112@mail.gmail.com> (raw)
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.
Many hunks are failing in each of the patch. I guess when the first is
failing others are
bound to..
Also, i m trying to apply the patches in the following order :
[patch 1] mm: PG_free flag
[patch 2] mm: speculative get_page
[patch 3] radix tree: lookup_slot
[patch 4] radix tree: lockless readside
[patch 5] mm: lockless pagecache lookups
[patch 6] mm: spinlock tree_lock
This sequence is correct....right?
Thanks,
Dave
next reply other threads:[~2005-06-28 11:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 11:56 David Kearster [this message]
2005-06-28 12:20 ` [rfc] lockless pagecache Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 6:29 Nick Piggin
2005-06-27 7:46 ` Andrew Morton
2005-06-27 8:02 ` Nick Piggin
2005-06-27 8:15 ` Andrew Morton
2005-06-27 8:28 ` Nick Piggin
2005-06-27 8:56 ` Lincoln Dale
2005-06-27 9:04 ` Nick Piggin
2005-06-27 18:14 ` Chen, Kenneth W
2005-06-27 18:50 ` Badari Pulavarty
2005-06-27 19:05 ` Chen, Kenneth W
2005-06-27 19:22 ` Christoph Lameter
2005-06-27 19:42 ` Chen, Kenneth W
2005-07-05 15:11 ` Sonny Rao
2005-07-05 15:31 ` Martin J. Bligh
2005-07-05 15:37 ` Sonny Rao
2005-06-27 13:17 ` Benjamin LaHaise
2005-06-28 0:32 ` Nick Piggin
2005-06-28 1:26 ` William Lee Irwin III
2005-06-27 14:08 ` Martin J. Bligh
2005-06-27 17:49 ` Christoph Lameter
2005-06-29 10:49 ` Hirokazu Takahashi
2005-06-29 11:38 ` Nick Piggin
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=3bba6cc4050628045676c61112@mail.gmail.com \
--to=david.kearster@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox