linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-mm@kvack.org
Subject: Re: [RFT][PATCH 2/2] pagefault scalability alternative
Date: Tue, 23 Aug 2005 21:20:02 +1000	[thread overview]
Message-ID: <430B0662.3060509@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0508230805040.5224@goblin.wat.veritas.com>

Hugh Dickins wrote:
> On Tue, 23 Aug 2005, Nick Piggin wrote:

>>I had preempt_disable() in tlb_gather_mmu which I thought was nice,
>>but maybe you don't?
> 
> 
> I most definitely agree.  tlb_gather_mmu uses smp_processor_id when it
> should be using get_cpu, we don't usually open code the preempt_disable.
> 

Yep.

> But there's a number of things peculiar about tlb_gather_mmu and friends
> (e.g. the rss but not anon_rss asymmetry; and what have those got to do
> with "tlb" anyway?), spread over several arches, I decided to stay away
> for now, go into all that at a later date.  What it should be doing
> about rss depends rather on what Christoph ends up with there.
> 

I agree. I think moving rss accounting out of the tlb operations
and into mm/memory.c is a good idea too. I don't think there are
any problems doing so, either.

But we won't get bogged down on that right now.

> 
>>>+#ifdef CONFIG_SPLIT_PTLOCK
>>>+#define __pte_lockptr(page)	((spinlock_t *)&((page)->private))
>>>+#define pte_lock_init(page)	spin_lock_init(__pte_lockptr(page))
>>>+#define pte_lock_deinit(page)	((page)->mapping = NULL)
>>
>>Do you mean page->private?
> 
> 
> No, it does mean page->mapping: depending on DEBUG options and whatnot,
> the spinlock_t might (currently, I think) be as many as 5 unsigned longs,
> hich happily just happen to fit into the unmodified 32-bit struct page,
> and the only "corruption" which actually matters is that freeing a page
> protests if page->mapping is found set.
> 

OK no worries. Just so long as you don't overwrite ->_count,
the lockless pagecache is happy ;)

Which brings up another issue - this surely conflicts rather
badly with PageReserved removal :( Not that there is anything
wrong with that, but I don't like to create these kinds of
problems for people...

Do we still want to remove PageReserved sooner rather than
later?

-- 
SUSE Labs, Novell Inc.

Send instant messages to your online friends http://au.messenger.yahoo.com 
--
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>

  reply	other threads:[~2005-08-23 11:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 21:27 [RFT][PATCH 0/2] " Hugh Dickins
2005-08-22 21:29 ` [RFT][PATCH 1/2] " Hugh Dickins
2005-08-22 21:31 ` [RFT][PATCH 2/2] " Hugh Dickins
2005-08-23  0:25   ` Nick Piggin
2005-08-23  7:22     ` Hugh Dickins
2005-08-23 11:20       ` Nick Piggin [this message]
2005-08-23 13:06         ` Hugh Dickins
2005-08-23 13:29           ` Nick Piggin
2005-08-23 16:38             ` Hugh Dickins
2005-08-23  5:39   ` Andi Kleen
2005-08-23  7:01     ` Hugh Dickins
2005-08-22 22:29 ` [RFT][PATCH 0/2] " Christoph Lameter
2005-08-23  0:32   ` Nick Piggin
2005-08-23  7:04     ` Hugh Dickins
2005-08-23  8:14   ` Hugh Dickins
2005-08-23 10:03     ` Nick Piggin
2005-08-23 16:30     ` Christoph Lameter
2005-08-23 16:43       ` Martin J. Bligh
2005-08-23 18:29       ` Hugh Dickins
2005-08-27 22:10       ` Avi Kivity

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=430B0662.3060509@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@osdl.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