From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Memory Management <linux-mm@kvack.org>
Subject: [patch 0/4] lockless pagecache for 2.6.18-mm3
Date: Wed, 4 Oct 2006 16:36:58 +0200 (CEST) [thread overview]
Message-ID: <20061004123018.5637.93004.sendpatchset@linux.site> (raw)
Updated lockless patchset against 2.6.18-mm3. Boots and survives basic
stress testing so far.
I have decided not to implement the tweak Hugh suggested yet, for reasons
outlined in the patch description. I still think it is a promising
approach, I just haven't been able to convince myself of correctness
in some paths yet.
Nick
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2006-10-04 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 14:36 Nick Piggin [this message]
2006-10-04 14:37 ` [patch 1/4] radix-tree: use indirect bit Nick Piggin
2006-10-04 14:37 ` [patch 2/4] radix-tree: gang_lookup_slot Nick Piggin
2006-10-04 14:37 ` [patch 3/4] mm: speculative get page Nick Piggin
2006-10-04 14:37 ` [patch 4/4] mm: lockless pagecache lookups 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=20061004123018.5637.93004.sendpatchset@linux.site \
--to=npiggin@suse.de \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.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