From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [rfc][patch 1/2] mnt_want_write speedup 1
Date: Thu, 18 Dec 2008 22:34:52 -0800 [thread overview]
Message-ID: <1229668492.17206.594.camel@nimitz> (raw)
In-Reply-To: <20081219061937.GA16268@wotan.suse.de>
On Fri, 2008-12-19 at 07:19 +0100, Nick Piggin wrote:
> Hi. Fun, chasing down performance regressions.... I wonder what people think
> about these patches? Is it OK to bloat struct vfsmount? Any races?
Very cool stuff, Nick. I especially like how much it simplifies things
and removes *SO* much code.
Bloating the vfsmount was one of the things that really, really tried to
avoid. When I start to think about the SGI machines, it gets me really
worried. I went to a lot of trouble to make sure that the per-vfsmount
memory overhead didn't scale with the number of cpus.
> This could
> be made even faster if mnt_make_readonly could tolerate a really high latency
> synchronize_rcu()... can it?)
Yes, I think it can tolerate it. There's a lot of work to do, and we
already have to go touch all the other per-cpu objects. There also
tends to be writeout when this happens, so I don't think a few seconds,
even, will be noticed.
> This patch speeds up lmbench lat_mmap test by about 8%. lat_mmap is set up
> basically to mmap a 64MB file on tmpfs, fault in its pages, then unmap it.
> A microbenchmark yes, but it exercises some important paths in the mm.
Do you know where the overhead actually came from? Was it the
spinlocks? Was removing all the atomic ops what really helped?
I'll take a more in-depth look at your code tomorrow and see if I see
any races.
-- Dave
--
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:[~2008-12-19 6:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 6:19 Nick Piggin
2008-12-19 6:20 ` [rfc][patch 2/2] mnt_want_write speedup 2 Nick Piggin
2008-12-19 6:34 ` Dave Hansen [this message]
2008-12-19 6:52 ` [rfc][patch 1/2] mnt_want_write speedup 1 Nick Piggin
2008-12-19 6:56 ` Nick Piggin
2008-12-19 6:54 ` Dave Hansen
2008-12-19 7:03 ` Nick Piggin
2008-12-19 15:32 ` Dave Hansen
2008-12-22 4:35 ` Nick Piggin
2008-12-29 23:00 ` Dave Hansen
2008-12-30 4:02 ` 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=1229668492.17206.594.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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