From: Jens Axboe <axboe@kernel.dk>
To: Matthew Wilcox <matthew@wil.cx>
Cc: "Jiang, Dave" <dave.jiang@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Foong, Annie" <annie.foong@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Nadolski, Edmund" <edmund.nadolski@intel.com>,
"Skirvin, Jeffrey D" <jeffrey.d.skirvin@intel.com>
Subject: Re: rq_affinity doesn't seem to work?
Date: Wed, 13 Jul 2011 20:00:46 +0200 [thread overview]
Message-ID: <4E1DDD4E.6040100@kernel.dk> (raw)
In-Reply-To: <20110713171011.GA11864@parisc-linux.org>
On 2011-07-13 19:10, Matthew Wilcox wrote:
> On Tue, Jul 12, 2011 at 10:30:35PM +0200, Jens Axboe wrote:
>> It's probably the grouping, we need to do something about that. Does the
>> below patch make it behave as you expect?
>
> "something", absolutely. But there is benefit from doing some aggregation
> (we tried disabling it entirely with the "well-known OLTP benchmark" and
> performance went down).
Yep, that's why the current solution is somewhat middle of the road...
> Ideally we'd do something like "if the softirq is taking up more than 10%
> of a core, split the grouping". Do we have enough stats to do that kind
> of monitoring?
I don't think we have those stats, though it could/should be pulled from
the ksoftirqX threads. We could have some metric, ala
dest_cpu = get_group_completion_cpu(rq->cpu);
if (ksoftirqd_of(dest_cpu) >= 90% busy)
dest_cpu = rq->cpu;
to send things completely local to the submitter of the IO, IFF the
current CPU is close to running at full tilt.
--
Jens Axboe
next prev parent reply other threads:[~2011-07-13 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 19:03 rq_affinity doesn't seem to work? Jiang, Dave
2011-07-12 20:30 ` Jens Axboe
2011-07-12 21:17 ` Jiang, Dave
2011-07-13 17:10 ` Matthew Wilcox
2011-07-13 18:00 ` Jens Axboe [this message]
2011-07-14 17:02 ` Roland Dreier
2011-07-15 20:20 ` Dan Williams
2011-07-15 23:43 ` ersatz splatt
2011-07-16 2:12 ` ersatz splatt
2011-07-16 2:40 ` Christoph Hellwig
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=4E1DDD4E.6040100@kernel.dk \
--to=axboe@kernel.dk \
--cc=annie.foong@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=edmund.nadolski@intel.com \
--cc=jeffrey.d.skirvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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