From: Jeffle Xu <jefflexu@linux.alibaba.com>
To: axboe@kernel.dk, hch@infradead.org, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
ming.lei@redhat.com, joseph.qi@linux.alibaba.com,
xiaoguang.wang@linux.alibaba.com
Subject: [PATCH v3 0/2] block, iomap: disable iopoll for split bio
Date: Fri, 16 Oct 2020 17:18:49 +0800 [thread overview]
Message-ID: <20201016091851.93728-1-jefflexu@linux.alibaba.com> (raw)
This patchset is to fix the potential hang occurred in sync polling.
Please refer the following link for background info and the v1 patch:
https://patchwork.kernel.org/project/linux-block/patch/20201013084051.27255-1-jefflexu@linux.alibaba.com/
The first patch disables iopoll for split bio in block layer, which is
suggested by Ming Lei.
The second patch disables iopoll when one dio need to be split into
multiple bios.
changes since v2:
- tune the line length of patch 1
- fix the condition checking whether split needed in patch 2
changes since v1:
- adopt the fix suggested by Ming Lei, to disable iopoll for split bio directly
- disable iopoll in direct IO routine of blkdev fs and iomap
Jeffle Xu (2):
block: disable iopoll for split bio
block,iomap: disable iopoll when split needed
block/blk-merge.c | 14 ++++++++++++++
fs/block_dev.c | 7 +++++++
fs/iomap/direct-io.c | 8 ++++++++
3 files changed, 29 insertions(+)
--
2.27.0
next reply other threads:[~2020-10-16 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 9:18 Jeffle Xu [this message]
2020-10-16 9:18 ` [PATCH v3 1/2] block: disable iopoll for split bio Jeffle Xu
2020-10-16 12:51 ` Ming Lei
2020-10-16 9:18 ` [PATCH v3 2/2] block,iomap: disable iopoll when split needed Jeffle Xu
2020-10-16 10:26 ` Ming Lei
2020-10-16 11:02 ` JeffleXu
2020-10-16 12:39 ` Ming Lei
2020-10-16 13:30 ` JeffleXu
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=20201016091851.93728-1-jefflexu@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xiaoguang.wang@linux.alibaba.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: 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).