From: Matthew Wilcox <matthew@wil.cx>
To: Jens Axboe <axboe@kernel.dk>
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 11:10:11 -0600 [thread overview]
Message-ID: <20110713171011.GA11864@parisc-linux.org> (raw)
In-Reply-To: <4E1CAEEB.8050506@kernel.dk>
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).
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?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2011-07-13 17:10 UTC|newest]
Thread overview: 13+ 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 19:03 ` Jiang, Dave
2011-07-12 20:30 ` Jens Axboe
2011-07-12 21:17 ` Jiang, Dave
2011-07-13 17:10 ` Matthew Wilcox [this message]
2011-07-13 18:00 ` Jens Axboe
2011-07-14 17:02 ` Roland Dreier
2011-07-14 17:02 ` Roland Dreier
2011-07-15 20:20 ` Dan Williams
2011-07-15 23:43 ` ersatz splatt
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=20110713171011.GA11864@parisc-linux.org \
--to=matthew@wil.cx \
--cc=annie.foong@intel.com \
--cc=axboe@kernel.dk \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.