linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Whitney <eric.whitney@hp.com>
To: Ted Ts'o <tytso@mit.edu>
Cc: Andi Kleen <andi@firstfloor.org>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Vivek Haldar <haldar@google.com>,
	Andreas Dilger <adilger@dilger.ca>,
	linux-ext4@vger.kernel.org
Subject: Re: [RFC, PATCH] Avoid hot statistics cache line in ext4 extent cache
Date: Fri, 13 Apr 2012 15:01:47 -0400	[thread overview]
Message-ID: <4F88781B.9090005@hp.com> (raw)
In-Reply-To: <20120413184823.GA5898@thunk.org>

On 04/13/2012 02:48 PM, Ted Ts'o wrote:
> On Fri, Apr 13, 2012 at 08:41:58PM +0200, Andi Kleen wrote:
>>> The reason why I ask this is we're seeing anything like this with Eric
>>> Whitney's 48 CPU scalability testing; we're not CPU bottlenecked, and
>>> I don't even see evidence of a larger than usual CPU utilization
>>> compared to other file systems.
>>
>> I bet Eric didn't test with this statistic counter.
>
> Huh?  You can't turn it off, and he's been doing regular scalability
> tests at least once per kernel release.

Yes, as recently as 3.4-rc1.  I saw Andi's patch, and tested it this 
week against that baseline with the ffsb profiles we've been using for 
ext4 (and other filesystem) scalability measurements.

I didn't get a noticeable delta for throughput or reported CPU 
utilization on my 48 core eight node NUMA test setup.  That said, I plan 
to look at this more closely to verify that my workloads should have 
seen a delta in the first place.  Ted knows them well, though.  It's 
worth noting that I've got plenty of free CPU capacity while running the 
workload, which differs from Andi's/Tim's description.

>
> Can you say a bit more about exactly how you are doing this test and
> what are the "other issues" where this is becoming a bottleneck?  If
> possible I'd like to ask Eric if he can add it to his regular
> scalability tests.

Yes, I'm certainly willing to do that if practical, and I'm curious to 
know more about what the workload looks like.

Eric

>
> Thanks,
>
> 						 - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2012-04-13 19:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 22:17 [RFC, PATCH] Avoid hot statistics cache line in ext4 extent cache Andi Kleen
2012-03-24  1:10 ` Andreas Dilger
2012-03-24  3:13   ` Andi Kleen
2012-03-26 22:26     ` Vivek Haldar
2012-03-26 23:00       ` Andi Kleen
2012-03-26 23:57         ` Ted Ts'o
2012-04-11 16:59           ` Andi Kleen
2012-04-13 17:42             ` Linus Torvalds
2012-04-13 17:53               ` Tim Chen
2012-04-13 18:08                 ` Linus Torvalds
2012-04-13 18:31                   ` Tim Chen
2012-04-13 18:33                     ` Linus Torvalds
2012-04-13 18:37                     ` Ted Ts'o
2012-04-13 18:41                       ` Andi Kleen
2012-04-13 18:48                         ` Ted Ts'o
2012-04-13 19:01                           ` Eric Whitney [this message]
2012-04-13 19:26                       ` Tim Chen
2012-04-13 19:33                         ` Ted Ts'o
2012-04-13 17:57               ` Andi Kleen
2012-04-13 18:06               ` Ted Ts'o
2012-04-13 18:22                 ` 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=4F88781B.9090005@hp.com \
    --to=eric.whitney@hp.com \
    --cc=adilger@dilger.ca \
    --cc=andi@firstfloor.org \
    --cc=haldar@google.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tim.c.chen@linux.intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).