From: Florian Fainelli <f.fainelli@gmail.com>
To: Nitesh Shetty <nj.shetty@samsung.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
viro@zeniv.linux.org.uk
Cc: linux-block@vger.kernel.org, axboe@fb.com,
linux-nvme@lists.infradead.org, joshi.k@samsung.com
Subject: Re: [PATCH] blk: optimization for classic polling
Date: Wed, 10 Oct 2018 11:52:57 -0700 [thread overview]
Message-ID: <6425d6fc-59d7-7ea0-487f-bb5d0985653c@gmail.com> (raw)
In-Reply-To: <3578876466-3733-1-git-send-email-nj.shetty@samsung.com>
On 05/29/2083 08:21 PM, Nitesh Shetty wrote:
> This removes the dependency on interrupts to wake up task. Set task
> state as TASK_RUNNING, if need_resched() returns true,
> while polling for IO completion.
> Earlier, polling task used to sleep, relying on interrupt to wake it up.
> This made some IO take very long when interrupt-coalescing is enabled in
> NVMe.
>
> Reference:
> http://lists.infradead.org/pipermail/linux-nvme/2018-February/015435.html
> Signed-off-by: Nitesh Shetty <nj.shetty@samsung.com>
There is something seriously wrong with the date on your computer, this
patch is dated from May 29th 2083,... I would not be surprised if it
messed up people's email client and you did not get any response because
of that...
--
Florian
prev parent reply other threads:[~2018-10-11 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180208143655epcas1p444bf34705526b7839a5a135f82761aad@epcas1p4.samsung.com>
2083-05-30 4:21 ` [PATCH] blk: optimization for classic polling Nitesh Shetty
2018-02-08 15:27 ` Keith Busch
2018-02-08 16:03 ` Sagi Grimberg
2018-02-12 15:50 ` Bart Van Assche
2018-02-20 13:21 ` Peter Zijlstra
2018-02-20 16:27 ` Keith Busch
2018-02-20 22:37 ` Jens Axboe
2018-02-21 8:32 ` Peter Zijlstra
2018-10-10 18:52 ` Florian Fainelli [this message]
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=6425d6fc-59d7-7ea0-487f-bb5d0985653c@gmail.com \
--to=f.fainelli@gmail.com \
--cc=axboe@fb.com \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nj.shetty@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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).