From: Johannes Thumshirn <jthumshirn@suse.de> To: John Garry <john.garry@huawei.com> Cc: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@fb.com>, linux-block@vger.kernel.org, Christoph Hellwig <hch@infradead.org>, Mike Snitzer <snitzer@redhat.com>, dm-devel@redhat.com, Bart Van Assche <bart.vanassche@sandisk.com>, Laurence Oberman <loberman@redhat.com>, Paolo Valente <paolo.valente@linaro.org>, Oleksandr Natalenko <oleksandr@natalenko.name>, Tom Nguyen <tom81094@gmail.com>, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, Omar Sandoval <osandov@fb.com>, Linuxarm <linuxarm@huawei.com> Subject: Re: [PATCH V5 00/14] blk-mq-sched: improve sequential I/O performance(part 1) Date: Tue, 10 Oct 2017 14:34:39 +0200 [thread overview] Message-ID: <20171010123439.7lzndy5qcjtmd56y@linux-x5ow.site> (raw) In-Reply-To: <cb622a02-5187-5ee0-bccd-e867e8e7ee7d@huawei.com> Hi John, On Tue, Oct 10, 2017 at 01:24:52PM +0100, John Garry wrote: > It's using cfq (for non-mq) and mq-deadline (obviously for mq). Please be aware that cfq and mq-deadline are _not_ comparable, for a realistic comparasion please use deadline and mq-deadline or cfq and bfq. > root@(none)$ pwd > /sys/devices/platform/HISI0162:01/host0/port-0:0/expander-0:0/port-0:0:7/end_device-0:0:7 > root@(none)$ more ./target0:0:3/0:0:3:0/block/sdd/queue/scheduler > noop [cfq] Maybe missing CONFIG_IOSCHED_DEADLINE? Thanks, Johannes -- Johannes Thumshirn Storage jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg GF: Felix Imend�rffer, Jane Smithard, Graham Norton HRB 21284 (AG N�rnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Thumshirn <jthumshirn@suse.de> To: John Garry <john.garry@huawei.com> Cc: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@fb.com>, linux-block@vger.kernel.org, Christoph Hellwig <hch@infradead.org>, Mike Snitzer <snitzer@redhat.com>, dm-devel@redhat.com, Bart Van Assche <bart.vanassche@sandisk.com>, Laurence Oberman <loberman@redhat.com>, Paolo Valente <paolo.valente@linaro.org>, Oleksandr Natalenko <oleksandr@natalenko.name>, Tom Nguyen <tom81094@gmail.com>, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, Omar Sandoval <osandov@fb.com>, Linuxarm <linuxarm@huawei.com> Subject: Re: [PATCH V5 00/14] blk-mq-sched: improve sequential I/O performance(part 1) Date: Tue, 10 Oct 2017 14:34:39 +0200 [thread overview] Message-ID: <20171010123439.7lzndy5qcjtmd56y@linux-x5ow.site> (raw) In-Reply-To: <cb622a02-5187-5ee0-bccd-e867e8e7ee7d@huawei.com> Hi John, On Tue, Oct 10, 2017 at 01:24:52PM +0100, John Garry wrote: > It's using cfq (for non-mq) and mq-deadline (obviously for mq). Please be aware that cfq and mq-deadline are _not_ comparable, for a realistic comparasion please use deadline and mq-deadline or cfq and bfq. > root@(none)$ pwd > /sys/devices/platform/HISI0162:01/host0/port-0:0/expander-0:0/port-0:0:7/end_device-0:0:7 > root@(none)$ more ./target0:0:3/0:0:3:0/block/sdd/queue/scheduler > noop [cfq] Maybe missing CONFIG_IOSCHED_DEADLINE? Thanks, Johannes -- Johannes Thumshirn Storage jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-10-10 12:34 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-30 10:27 [PATCH V5 00/14] blk-mq-sched: improve sequential I/O performance(part 1) Ming Lei 2017-09-30 10:27 ` [PATCH V5 1/7] blk-mq: issue rq directly in blk_mq_request_bypass_insert() Ming Lei 2017-10-03 8:58 ` Christoph Hellwig 2017-10-03 13:39 ` Ming Lei 2017-09-30 10:27 ` [PATCH V5 2/7] blk-mq-sched: fix scheduler bad performance Ming Lei 2017-10-02 14:19 ` Christoph Hellwig 2017-09-30 10:27 ` [PATCH V5 3/7] sbitmap: introduce __sbitmap_for_each_set() Ming Lei 2017-09-30 10:27 ` [PATCH V5 4/7] blk-mq: introduce blk_mq_dequeue_from_ctx() Ming Lei 2017-10-03 9:01 ` Christoph Hellwig 2017-10-09 4:36 ` Ming Lei 2017-09-30 10:27 ` [PATCH V5 5/7] blk-mq-sched: move actual dispatching into one helper Ming Lei 2017-10-02 14:19 ` Christoph Hellwig 2017-10-09 9:07 ` Ming Lei 2017-09-30 10:27 ` [PATCH V5 6/7] blk-mq-sched: improve dispatching from sw queue Ming Lei 2017-10-03 9:05 ` Christoph Hellwig 2017-10-09 10:15 ` Ming Lei 2017-09-30 10:27 ` [PATCH V5 7/7] blk-mq-sched: don't dequeue request until all in ->dispatch are flushed Ming Lei 2017-10-03 9:11 ` Christoph Hellwig 2017-10-09 10:40 ` Ming Lei 2017-09-30 10:32 ` [PATCH V5 00/14] blk-mq-sched: improve sequential I/O performance(part 1) Ming Lei 2017-10-09 12:09 ` John Garry 2017-10-09 12:09 ` John Garry 2017-10-09 15:04 ` Ming Lei 2017-10-10 1:46 ` Ming Lei 2017-10-10 12:24 ` John Garry 2017-10-10 12:24 ` John Garry 2017-10-10 12:34 ` Johannes Thumshirn [this message] 2017-10-10 12:34 ` Johannes Thumshirn 2017-10-10 12:37 ` Paolo Valente 2017-10-10 12:37 ` Paolo Valente 2017-10-10 13:45 ` Ming Lei 2017-10-10 15:10 ` John Garry 2017-10-10 15:10 ` John Garry
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=20171010123439.7lzndy5qcjtmd56y@linux-x5ow.site \ --to=jthumshirn@suse.de \ --cc=axboe@fb.com \ --cc=bart.vanassche@sandisk.com \ --cc=dm-devel@redhat.com \ --cc=hch@infradead.org \ --cc=john.garry@huawei.com \ --cc=linux-block@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-scsi@vger.kernel.org \ --cc=linuxarm@huawei.com \ --cc=loberman@redhat.com \ --cc=ming.lei@redhat.com \ --cc=oleksandr@natalenko.name \ --cc=osandov@fb.com \ --cc=paolo.valente@linaro.org \ --cc=snitzer@redhat.com \ --cc=tom81094@gmail.com \ /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: linkBe 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.