From: Jens Axboe <jens.axboe@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>,
mszeredi@suse.de
Subject: Re: Performance regression in IO scheduler still there
Date: Fri, 13 Nov 2009 08:45:17 +0100 [thread overview]
Message-ID: <20091113074516.GR8742@kernel.dk> (raw)
In-Reply-To: <x49hbszpi7m.fsf@segfault.boston.devel.redhat.com>
On Thu, Nov 12 2009, Jeff Moyer wrote:
> Jens Axboe <jens.axboe@oracle.com> writes:
>
> > On Thu, Nov 12 2009, Jeff Moyer wrote:
> >> Good question. ;-) I grep for NCQ in dmesg output and make sure it's
> >> greater than 0/32. There may be a better way, though.
> >
> > cat /sys/block/<dev>/device/queue_depth
> >
> > :-)
>
> OK, your comment about only working for SCSI disks threw me off.
> Perhaps you meant only works for devices that use the sd driver?
Yeah, only works for storage that plugs into the SCSI stack.
--
Jens Axboe
next prev parent reply other threads:[~2009-11-13 7:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 17:20 Performance regression in IO scheduler still there Jan Kara
2009-10-26 17:26 ` Jeff Moyer
2009-11-05 20:10 ` Jeff Moyer
2009-11-05 23:00 ` Corrado Zoccolo
2009-11-06 14:14 ` Jeff Moyer
2009-11-10 18:37 ` Jan Kara
2009-11-06 18:56 ` Jeff Moyer
2009-11-08 17:01 ` Corrado Zoccolo
2009-11-10 16:47 ` Jeff Moyer
2009-11-10 17:37 ` Corrado Zoccolo
2009-11-11 14:10 ` Jan Kara
2009-11-11 17:43 ` Jeff Moyer
2009-11-12 17:29 ` Jan Kara
2009-11-12 20:44 ` Jeff Moyer
2009-11-12 21:00 ` Jens Axboe
2009-11-12 21:05 ` Jeff Moyer
2009-11-13 7:45 ` Jens Axboe [this message]
2009-11-16 10:47 ` Jan Kara
2009-11-16 16:58 ` Jan Kara
2009-11-16 17:03 ` Jeff Moyer
2009-11-16 18:38 ` Corrado Zoccolo
2009-11-16 22:17 ` Jan Kara
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=20091113074516.GR8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=efault@gmx.de \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.de \
/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