From: Fam Zheng <famz@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 5/8] block/raw-posix: refactor handle_aiocb_write_zeroes a bit
Date: Mon, 5 Jan 2015 14:57:26 +0800 [thread overview]
Message-ID: <20150105065726.GB1800@ad.nay.redhat.com> (raw)
In-Reply-To: <1419931250-19259-6-git-send-email-den@openvz.org>
On Tue, 12/30 12:20, Denis V. Lunev wrote:
> move code dealing with a block device to a separate function. This will
> allow to implement additional processing for an ordinary files.
s/an//
>
> Pls note, that xfs_code has been moved before checking for
> s->has_write_zeroes as xfs_write_zeroes does not touch this flag inside.
> This makes code a bit more consistent.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Kevin Wolf <kwolf@redhat.com>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> CC: Peter Lieven <pl@kamp.de>
> ---
> block/raw-posix.c | 60 +++++++++++++++++++++++++++++++++++--------------------
> 1 file changed, 38 insertions(+), 22 deletions(-)
>
> diff --git a/block/raw-posix.c b/block/raw-posix.c
> index 25a6947..7866d31 100644
> --- a/block/raw-posix.c
> +++ b/block/raw-posix.c
> @@ -915,46 +915,62 @@ static int do_fallocate(int fd, int mode, off_t offset, off_t len)
> }
> #endif
>
> -static ssize_t handle_aiocb_write_zeroes(RawPosixAIOData *aiocb)
> +static ssize_t handle_aiocb_write_zeroes_block(RawPosixAIOData *aiocb)
> {
> int ret = -EOPNOTSUPP;
> BDRVRawState *s = aiocb->bs->opaque;
>
> - if (s->has_write_zeroes == 0) {
> + if (!s->has_write_zeroes) {
> return -ENOTSUP;
> }
>
> - if (aiocb->aio_type & QEMU_AIO_BLKDEV) {
> #ifdef BLKZEROOUT
> - do {
> - uint64_t range[2] = { aiocb->aio_offset, aiocb->aio_nbytes };
> - if (ioctl(aiocb->aio_fildes, BLKZEROOUT, range) == 0) {
> - return 0;
> - }
> - } while (errno == EINTR);
> -
> - ret = -errno;
> -#endif
> - } else {
> -#ifdef CONFIG_XFS
> - if (s->is_xfs) {
> - return xfs_write_zeroes(s, aiocb->aio_offset, aiocb->aio_nbytes);
> + do {
> + uint64_t range[2] = { aiocb->aio_offset, aiocb->aio_nbytes };
> + if (ioctl(aiocb->aio_fildes, BLKZEROOUT, range) == 0) {
> + return 0;
> }
> -#endif
> + } while (errno == EINTR);
>
> -#ifdef CONFIG_FALLOCATE_ZERO_RANGE
> - ret = do_fallocate(s->fd, FALLOC_FL_ZERO_RANGE,
> - aiocb->aio_offset, aiocb->aio_nbytes);
> + ret = translate_err(-errno);
> #endif
> - }
>
> - ret = translate_err(ret);
> if (ret == -ENOTSUP) {
> s->has_write_zeroes = false;
> }
> return ret;
> }
>
> +static ssize_t handle_aiocb_write_zeroes(RawPosixAIOData *aiocb)
> +{
> + BDRVRawState *s;
> +
> + if (aiocb->aio_type & QEMU_AIO_BLKDEV) {
> + return handle_aiocb_write_zeroes_block(aiocb);
> + }
> +
> +#ifdef CONFIG_XFS
> + if (s->is_xfs) {
s is not initialized here.
Also, could you please do these refactoring before adding new code in the
series? That way the new code needn't to be moved, which makes the patches
easier to review.
Fam
> + return xfs_write_zeroes(s, aiocb->aio_offset, aiocb->aio_nbytes);
> + }
> +#endif
> +
> + s = aiocb->bs->opaque;
> +
> +#ifdef CONFIG_FALLOCATE_ZERO_RANGE
> + if (s->has_write_zeroes) {
> + int ret = do_fallocate(s->fd, FALLOC_FL_ZERO_RANGE,
> + aiocb->aio_offset, aiocb->aio_nbytes);
> + if (ret == 0 && ret != -ENOTSUP) {
> + return ret;
> + }
> + }
> +#endif
> +
> + s->has_write_zeroes = false;
> + return -ENOTSUP;
> +}
> +
> static ssize_t handle_aiocb_discard(RawPosixAIOData *aiocb)
> {
> int ret = -EOPNOTSUPP;
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2015-01-05 6:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 9:20 [Qemu-devel] [PATCH v3 0/8] eliminate data write in bdrv_write_zeroes on Linux in raw-posix.c Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 1/8] block: prepare bdrv_co_do_write_zeroes to deal with large bl.max_write_zeroes Denis V. Lunev
2015-01-05 7:34 ` Peter Lieven
2015-01-05 11:06 ` Denis V. Lunev
2015-01-05 11:23 ` Peter Lieven
2015-01-05 11:48 ` Denis V. Lunev
2015-01-05 12:26 ` [Qemu-devel] [PATCH v2 1/1] " Denis V. Lunev
2015-01-05 12:32 ` [Qemu-devel] [PATCH v3 " Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 2/8] block: use fallocate(FALLOC_FL_ZERO_RANGE) in handle_aiocb_write_zeroes Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 3/8] block/raw-posix: create do_fallocate helper Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 4/8] block/raw-posix: create translate_err helper to merge errno values Denis V. Lunev
2015-01-05 6:46 ` Fam Zheng
2015-01-05 11:17 ` Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 5/8] block/raw-posix: refactor handle_aiocb_write_zeroes a bit Denis V. Lunev
2015-01-05 6:57 ` Fam Zheng [this message]
2015-01-05 11:07 ` Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 6/8] block: use fallocate(FALLOC_FL_PUNCH_HOLE) & fallocate(0) to write zeroes Denis V. Lunev
2015-01-05 7:02 ` Fam Zheng
2015-01-05 11:14 ` Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 7/8] block/raw-posix: call plain fallocate in handle_aiocb_write_zeroes Denis V. Lunev
2014-12-30 9:20 ` [Qemu-devel] [PATCH 8/8] block/raw-posix: set max_write_zeroes to INT_MAX for regular files Denis V. Lunev
2014-12-30 10:55 ` [Qemu-devel] [PATCH v3 0/8] eliminate data write in bdrv_write_zeroes on Linux in raw-posix.c Peter Lieven
2014-12-30 11:07 ` Denis V. Lunev
2015-01-05 6:55 ` Peter Lieven
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=20150105065726.GB1800@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=den@openvz.org \
--cc=kwolf@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).