From: Kanchan Joshi <joshi.k@samsung.com>
To: axboe@kernel.dk, kbusch@kernel.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@lst.de, Damien.LeMoal@wdc.com,
Kanchan Joshi <joshi.k@samsung.com>
Subject: [PATCH 0/2] fix/extend zone-append in block-layer
Date: Thu, 2 Jul 2020 21:08:48 +0530 [thread overview]
Message-ID: <1593704330-11540-1-git-send-email-joshi.k@samsung.com> (raw)
In-Reply-To: CGME20200702154204epcas5p15106774a3d556b77050710722da89922@epcas5p1.samsung.com
First patch is about returning failure (rather than success) when
max_append_sectors is 0. This prevents bio_iov_iter_get_pages() from
getting into an endless loop.
Second patch enables issuing zone-append with iov_iter of bvec type.
It adds a helper which is similar to __bio_iov_bvec_add_pages() but
takes zone-append limits into account.
Kanchan Joshi (2):
block: fix error code for zone-append
block: enable zone-append for iov_iter of bvec type
block/bio.c | 33 +++++++++++++++++++++++++++++----
1 file changed, 29 insertions(+), 4 deletions(-)
--
2.7.4
next parent reply other threads:[~2020-07-02 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200702154204epcas5p15106774a3d556b77050710722da89922@epcas5p1.samsung.com>
2020-07-02 15:38 ` Kanchan Joshi [this message]
[not found] ` <CGME20200702154208epcas5p39fe202f642a9d5c8dde9b911645c594c@epcas5p3.samsung.com>
2020-07-02 15:38 ` [PATCH 1/2] block: fix error code for zone-append Kanchan Joshi
2020-07-03 5:29 ` Damien Le Moal
2020-07-03 6:20 ` Kanchan Joshi
[not found] ` <CGME20200702154213epcas5p4e8d42861cb5ae91ddeccf1ed73107304@epcas5p4.samsung.com>
2020-07-02 15:38 ` [PATCH 2/2] block: enable zone-append for iov_iter of bvec type Kanchan Joshi
2020-07-03 5:32 ` Damien Le Moal
2020-07-03 6:53 ` Kanchan Joshi
2020-07-03 8:07 ` Damien Le Moal
2020-07-03 13:02 ` Johannes Thumshirn
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=1593704330-11540-1-git-send-email-joshi.k@samsung.com \
--to=joshi.k@samsung.com \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).