From: Kashyap Desai <kashyap.desai@broadcom.com>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, axboe@kernel.dk,
Christoph Hellwig <hch@infradead.org>,
paolo.valente@linaro.org
Subject: RE: Device or HBA level QD throttling creates randomness in sequetial workload
Date: Mon, 24 Oct 2016 18:35:01 +0530 [thread overview]
Message-ID: <1f7cec69e6e12b6baa8e7f180a8e41b3@mail.gmail.com> (raw)
In-Reply-To: <20161021213121.GA10030@vader.DHCP.thefacebook.com>
>
> On Fri, Oct 21, 2016 at 05:43:35PM +0530, Kashyap Desai wrote:
> > Hi -
> >
> > I found below conversation and it is on the same line as I wanted some
> > input from mailing list.
> >
> > http://marc.info/?l=linux-kernel&m=147569860526197&w=2
> >
> > I can do testing on any WIP item as Omar mentioned in above
discussion.
> > https://github.com/osandov/linux/tree/blk-mq-iosched
I tried build kernel using this repo, but looks like it is not allowed to
reboot due to some changes in <block> layer.
>
> Are you using blk-mq for this disk? If not, then the work there won't
affect you.
YES. I am using blk-mq for my test. I also confirm if use_blk_mq is
disable, Sequential work load issue is not seen and <cfq> scheduling works
well.
>
> > Is there any workaround/alternative in latest upstream kernel, if user
> > wants to see limited penalty for Sequential Work load on HDD ?
> >
> > ` Kashyap
> >
next prev parent reply other threads:[~2016-10-24 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:13 Device or HBA level QD throttling creates randomness in sequetial workload Kashyap Desai
2016-10-21 21:31 ` Omar Sandoval
2016-10-24 13:05 ` Kashyap Desai [this message]
2016-10-24 15:41 ` Omar Sandoval
-- strict thread matches above, loose matches on Subject: below --
2016-10-24 18:54 Kashyap Desai
2016-10-26 20:56 ` Omar Sandoval
2016-10-31 17:24 ` Jens Axboe
2016-11-01 5:40 ` Kashyap Desai
2017-01-30 13:52 ` Kashyap Desai
2017-01-30 16:30 ` Bart Van Assche
2017-01-30 16:32 ` Jens Axboe
2017-01-30 18:28 ` Kashyap Desai
2017-01-30 18:29 ` Jens Axboe
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=1f7cec69e6e12b6baa8e7f180a8e41b3@mail.gmail.com \
--to=kashyap.desai@broadcom.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=paolo.valente@linaro.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).