From: Kevin Wolf <kwolf@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Fam Zheng <famz@redhat.com>, Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 7/7] block/raw-posix: set max_write_zeroes to INT_MAX for regular files
Date: Mon, 2 Feb 2015 14:23:55 +0100 [thread overview]
Message-ID: <20150202132355.GC9478@noname.redhat.com> (raw)
In-Reply-To: <1422607337-25335-8-git-send-email-den@openvz.org>
Am 30.01.2015 um 09:42 hat Denis V. Lunev geschrieben:
> fallocate() works fine and could handle properly with arbitrary size
> requests. There is no sense to reduce the amount of space to fallocate.
> The bigger is the size, the better is the performance as the amount of
> journal updates is reduced.
>
> The patch changes behavior for both generic filesystem and XFS codepaths,
> which are different in handle_aiocb_write_zeroes. The implementation
> of fallocate and xfsctl(XFS_IOC_ZERO_RANGE) for XFS are exactly the same
> thus the change is fine for both ways.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> Reviewed-by: Max Reitz <mreitz@redhat.com>
> CC: Kevin Wolf <kwolf@redhat.com>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> CC: Peter Lieven <pl@kamp.de>
> CC: Fam Zheng <famz@redhat.com>
> ---
> block/raw-posix.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/block/raw-posix.c b/block/raw-posix.c
> index 7b42f37..933c778 100644
> --- a/block/raw-posix.c
> +++ b/block/raw-posix.c
> @@ -293,6 +293,20 @@ static void raw_probe_alignment(BlockDriverState *bs, int fd, Error **errp)
> }
> }
>
> +static void raw_probe_max_write_zeroes(BlockDriverState *bs)
> +{
> + BDRVRawState *s = bs->opaque;
> + struct stat st;
> +
> + if (fstat(s->fd, &st) < 0) {
> + return; /* no problem, keep default value */
> + }
> + if (!S_ISREG(st.st_mode) || !s->discard_zeroes) {
> + return;
> + }
> + bs->bl.max_write_zeroes = INT_MAX;
> +}
Peter, do you remember why INT_MAX isn't actually the default? I think
the most reasonable behaviour would be that a limitation is only used if
a block driver requests it, and otherwise unlimited is assumed.
We can take this patch to raw-posix, it is certainly not wrong. But any
format driver or filter will still, in most cases needlessly, apply
MAX_WRITE_ZEROES_DEFAULT, i.e. a 16 MB maximum, so I think we should
consider making a change to the default.
Kevin
next prev parent reply other threads:[~2015-02-02 13:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 8:42 [Qemu-devel] [PATCH v6 0/7] eliminate data write in bdrv_write_zeroes on Linux in raw-posix.c Denis V. Lunev
2015-01-30 8:42 ` [Qemu-devel] [PATCH 1/7] block/raw-posix: create translate_err helper to merge errno values Denis V. Lunev
2015-01-30 8:44 ` Peter Lieven
2015-01-30 8:42 ` [Qemu-devel] [PATCH 2/7] block/raw-posix: create do_fallocate helper Denis V. Lunev
2015-01-30 8:47 ` Peter Lieven
2015-01-30 8:49 ` Denis V. Lunev
2015-01-30 8:50 ` Peter Lieven
2015-01-30 8:42 ` [Qemu-devel] [PATCH 3/7] block/raw-posix: refactor handle_aiocb_write_zeroes a bit Denis V. Lunev
2015-01-30 8:42 ` [Qemu-devel] [PATCH 4/7] block: use fallocate(FALLOC_FL_ZERO_RANGE) in handle_aiocb_write_zeroes Denis V. Lunev
2015-01-30 8:42 ` [Qemu-devel] [PATCH 5/7] block/raw-posix: call plain fallocate " Denis V. Lunev
2015-01-30 14:58 ` Max Reitz
2015-01-30 15:41 ` Denis V. Lunev
2015-01-30 15:42 ` Max Reitz
2015-01-30 15:53 ` Denis V. Lunev
2015-01-30 8:42 ` [Qemu-devel] [PATCH 6/7] block: use fallocate(FALLOC_FL_PUNCH_HOLE) & fallocate(0) to write zeroes Denis V. Lunev
2015-01-30 15:02 ` Max Reitz
2015-01-30 8:42 ` [Qemu-devel] [PATCH 7/7] block/raw-posix: set max_write_zeroes to INT_MAX for regular files Denis V. Lunev
2015-02-02 13:23 ` Kevin Wolf [this message]
2015-02-02 13:55 ` Peter Lieven
2015-02-02 14:04 ` Kevin Wolf
2015-02-02 14:12 ` Peter Lieven
2015-02-02 14:16 ` Kevin Wolf
2015-02-02 14:20 ` Peter Lieven
2015-02-02 14:38 ` Denis V. Lunev
2015-02-02 14:49 ` Kevin Wolf
2015-02-02 15:30 ` Denis V. Lunev
2015-02-02 13:26 ` [Qemu-devel] [PATCH v6 0/7] eliminate data write in bdrv_write_zeroes on Linux in raw-posix.c Kevin Wolf
-- strict thread matches above, loose matches on Subject: below --
2015-01-28 18:38 [Qemu-devel] [PATCH v5 " Denis V. Lunev
2015-01-28 18:38 ` [Qemu-devel] [PATCH 7/7] block/raw-posix: set max_write_zeroes to INT_MAX for regular files Denis V. Lunev
2015-01-29 22:51 ` Max Reitz
2015-01-27 13:51 [Qemu-devel] [PATCH v4 0/7] eliminate data write in bdrv_write_zeroes on Linux in raw-posix.c Denis V. Lunev
2015-01-27 13:51 ` [Qemu-devel] [PATCH 7/7] block/raw-posix: set max_write_zeroes to INT_MAX for regular files Denis V. Lunev
2015-01-27 18:05 ` Max Reitz
2015-01-27 18:11 ` Denis V. Lunev
2015-01-28 6:39 ` Denis V. Lunev
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=20150202132355.GC9478@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=den@openvz.org \
--cc=famz@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).