From: Christoph Lameter <clameter@sgi.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-mm@kvack.org, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [PATCH 00/16] concurrent pagecache (against 2.6.19-rt)
Date: Mon, 11 Dec 2006 11:03:13 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612111100300.2253@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20061207161800.426936000@chello.nl>
On Thu, 7 Dec 2006, Peter Zijlstra wrote:
> Based on Nick's lockless (read-side) pagecache patches (included in the series)
> here an attempt to make the write side concurrent.
On first glance it looks quite interesting and very innovative. Removing
the tree_lock completely also reduces cache line usage. The page struct
cacheline is already references in most contexts.
> Comment away ;-)
Could you post Nick's patches from your email addres and add a From Nick
line in them? Its a bit confusing to have a patchset with different
originating email addresses. Or does this come about by the evil header
mangling of the list processor? Maybe you need to use >From ??
--
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 prev parent reply other threads:[~2006-12-11 19:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 16:18 Peter Zijlstra
2006-12-07 16:18 ` [PATCH 01/16] radix-tree: RCU lockless readside Nick Piggin
2006-12-07 16:18 ` [PATCH 02/16] radix-tree: use indirect bit Nick Piggin
2006-12-07 16:18 ` [PATCH 03/16] radix-tree: gang_lookup_slot Nick Piggin
2006-12-07 16:18 ` [PATCH 04/16] radix-tree: gang_lookup_tag_slot Peter Zijlstra
2006-12-07 16:18 ` [PATCH 05/16] mm: speculative get page Nick Piggin
2006-12-07 16:18 ` [PATCH 06/16] mm: lockless pagecache lookups Nick Piggin
2006-12-07 16:18 ` [PATCH 07/16] mm: fix speculative page get preemption bug Peter Zijlstra
2006-12-07 16:18 ` [PATCH 08/16] mm: speculative page get for PREEMPT_RT Peter Zijlstra
2006-12-07 16:18 ` [PATCH 09/16] mm: speculative find_get_pages_tag Peter Zijlstra
2006-12-07 16:18 ` [PATCH 10/16] mm: remove find_tylock_page Peter Zijlstra
2006-12-07 16:18 ` [PATCH 11/16] mm: change tree_lock into a spinlock Peter Zijlstra
2006-12-07 16:18 ` [PATCH 12/16] radix-tree: concurrent write side support Peter Zijlstra
2006-12-07 16:18 ` [PATCH 13/16] atomic_ulong_t Peter Zijlstra
2006-12-07 16:18 ` [PATCH 14/16] mm/fs: abstract address_space::nrpages Peter Zijlstra
2006-12-07 16:18 ` [PATCH 15/16] mm: lock_page_ref Peter Zijlstra
2006-12-07 16:18 ` [PATCH 16/16] mm: concurrent pagecache write side Peter Zijlstra
2006-12-11 19:03 ` Christoph Lameter [this message]
2006-12-11 19:24 ` [PATCH 00/16] concurrent pagecache (against 2.6.19-rt) Peter Zijlstra
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=Pine.LNX.4.64.0612111100300.2253@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-mm@kvack.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