linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <ak@linux.intel.com>, Andi Kleen <andi@firstfloor.org>,
	linux-mm@kvack.org, Andrea Arcangeli <aarcange@redhat.com>,
	Rik van Riel <riel@redhat.com>,
	tim.c.chen@linux.intel.com, torvalds@linux-foundation.org,
	lwoodman@redhat.com, mel@csn.ul.ie
Subject: Re: [PATCH 1/4] VM/RMAP: Add infrastructure for batching the rmap chain locking
Date: Tue, 10 May 2011 01:02:55 +0200	[thread overview]
Message-ID: <20110509230255.GA6008@one.firstfloor.org> (raw)
In-Reply-To: <20110509152841.ec957d23.akpm@linux-foundation.org>

On Mon, May 09, 2011 at 03:28:41PM -0700, Andrew Morton wrote:
> On Mon, 09 May 2011 15:23:03 -0700
> Andi Kleen <ak@linux.intel.com> wrote:
> 
> > > After fixing that and doing an allnoconfig x86_64 build, the patchset
> > > takes rmap.o's .text from 6167 bytes to 6551.  This is likely to be a
> > > regression for uniprocessor machines.  What can we do about this?
> > >
> > 
> > Regression in what way?
> 
> It makes the code larger and probably slower, for no gain?

It should be actually faster because there are much less atomic ops.
Atomic ops are quite expensive -- especially on some older CPUs, even when
not contended.

> 
> > I guess I can move some of the functions out of 
> > line.
> 
> I don't know how much that will help.  Perhaps a wholesale refactoring
> and making it all SMP-only will be justified.  

Yes I don't think there were a lot of callers.

I can take out the lockbreak. I was a bit dubious on its utility
anyways.

-Andi

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-05-09 23:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05 19:32 Batch locking for rmap fork/exit processing Andi Kleen
2011-05-05 19:32 ` [PATCH 1/4] VM/RMAP: Add infrastructure for batching the rmap chain locking Andi Kleen
2011-05-06 15:59   ` Rik van Riel
2011-05-09 21:43   ` Andrew Morton
2011-05-09 22:23     ` Andi Kleen
2011-05-09 22:28       ` Andrew Morton
2011-05-09 23:02         ` Andi Kleen [this message]
2011-05-09 23:16           ` Andrew Morton
2011-05-10  0:05             ` Andi Kleen
2011-05-10  1:26               ` Andrew Morton
2011-05-10  1:27                 ` Rik van Riel
2011-05-10  1:48                   ` Andrew Morton
2011-05-05 19:32 ` [PATCH 2/4] VM/RMAP: Batch anon vma chain root locking in fork Andi Kleen
2011-05-06 15:59   ` Rik van Riel
2011-05-05 19:32 ` [PATCH 3/4] VM/RMAP: Batch anon_vma_unlink in exit Andi Kleen
2011-05-06 16:48   ` Rik van Riel
2011-05-05 19:32 ` [PATCH 4/4] VM/RMAP: Move avc freeing outside the lock Andi Kleen
2011-05-06 16:52   ` Rik van Riel
2011-05-06 16:44 ` Batch locking for rmap fork/exit processing Linus Torvalds
2011-05-06 17:05   ` Andi Kleen

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=20110509230255.GA6008@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=aarcange@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=lwoodman@redhat.com \
    --cc=mel@csn.ul.ie \
    --cc=riel@redhat.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.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