From: Tim Chen <tim.c.chen@linux.intel.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] tmpfs: Improve tmpfs scalability
Date: Fri, 21 May 2010 09:07:47 -0700 [thread overview]
Message-ID: <1274458067.31973.8955.camel@mudge.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1005201837040.21050@tigran.mtv.corp.google.com>
On Thu, 2010-05-20 at 18:55 -0700, Hugh Dickins wrote:
>
> Interesting, thank you - I'll take a look, but not this week.
>
> I do hope you're using Aim7 just as an example: you know that mounting
> tmpfs with nr_blocks=0,nr_inodes=0 skips those shmem_sb_info updates
> altogether? Mounting in such a way should be fine for getting better
> numbers out of Aim7; but yes, there are reallife uses for tmpfs which
> are safer with the nr_blocks,nr_inodes limits.
>
Yes, Aim7 was provided as an example to illustrate the locking
bottleneck when blocks limit are imposed.
Tim
prev parent reply other threads:[~2010-05-21 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 23:34 tim
2010-05-19 9:27 ` Andi Kleen
2010-05-21 1:55 ` Hugh Dickins
2010-05-21 16:07 ` Tim Chen [this message]
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=1274458067.31973.8955.camel@mudge.jf.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome