From: Jeff Moyer <jmoyer@redhat.com>
To: asamymuthupa@micron.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org
Subject: Re: New driver mtipx2xx submission
Date: Wed, 15 Jun 2011 10:43:56 -0400 [thread overview]
Message-ID: <x49ips75f4j.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4DF80ADE.8020206@micron.com> (Asai Thambi S. P.'s message of "Tue, 14 Jun 2011 19:29:02 -0600")
Asai Thambi S P <asamymuthupa@micron.com> writes:
> On 6/1/2011 2:21 PM, Alan Cox wrote:
>>> Thanks, Asai! I don't think cfq is the ideal I/O scheduler to be
>>> testing. Could you run again with deadline and/or noop and see how that
>>> changes your throughput and perf report? Also, just for completeness,
>>> could you tell us which kernel you ran this against?
>
> kernel 2.6.38.6
>> How many processors is this system, just looking at the lock contention
>> which is pretty horrible.
>
> 8 processors (2 quad-core CPUs)
> Intel(R) Xeon(R) CPU X5672 @ 3.20GHz
>
[...]
> On looking into the data in below links, lock and block queue are
> consuming more time when running with ahci driver. Correct me if I
> missing something.
2.6.39 introduced the on-stack plugging work from Jens, the intent of
which is to reduce queue lock contention. It would be great if you
could run with that kernel and noop to see if we make up some of the
performance gap (which looks to be just north of 10%).
Asai, thanks for running these tests and providing all of this data!
-Jeff
next prev parent reply other threads:[~2011-06-15 14:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 15:53 New driver mtipx2xx submission Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-04-28 22:06 ` Alan Cox
2011-05-02 12:40 ` Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-05-02 17:42 ` Alan Cox
2011-05-03 20:07 ` [PATCH 0/3] " Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-05-11 17:40 ` Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-05-11 19:20 ` Alan Cox
2011-05-21 2:26 ` Asai Thambi S P
2011-05-25 14:36 ` Jeff Moyer
[not found] ` <22A973199D2C2F46933448F6E7990A300239EA77@ntxboimbx31.micron.com>
2011-06-01 19:51 ` Jeff Moyer
2011-06-01 20:21 ` Alan Cox
2011-06-15 1:29 ` Asai Thambi S P
2011-06-15 14:43 ` Jeff Moyer [this message]
2011-06-27 23:38 ` Asai Thambi Samymuthu Pattrayasamy (asamymuthupa) [CONTRACTOR]
2011-06-28 15:18 ` Jeff Moyer
2011-06-28 15:31 ` Alan Cox
2011-06-28 15:38 ` Jeff Moyer
2011-07-06 21:43 ` Asai Thambi S P
2011-07-07 7:37 ` Alan Cox
2011-07-26 10:46 ` Alan Cox
2011-07-26 11:44 ` Christoph Hellwig
2011-07-26 11:49 ` Alan Cox
2011-07-26 18:50 ` Jeff Garzik
2011-07-29 18:13 ` Asai Thambi S P
2011-08-11 18:36 ` Asai Thambi S P
2011-07-06 21:39 ` Asai Thambi S P
2011-06-02 1:21 ` David Dillow
2011-06-15 1:33 ` Asai Thambi S P
2011-06-15 3:12 ` David Dillow
2011-05-02 18:40 ` Jeff Moyer
2011-05-02 18:52 ` Alan Cox
2011-05-03 15:04 ` Mark Lord
2011-05-03 15:07 ` Alan Cox
2011-05-03 15:08 ` Mark Lord
2011-05-03 15:02 ` Mark Lord
2011-05-12 14:39 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2011-05-03 11:09 Jordan_Hargrave
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=x49ips75f4j.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=asamymuthupa@micron.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).