From: Eric Sandeen <sandeen@sandeen.net>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH V3] libxfs: use FALLOC_FL_ZERO_RANGE in libxfs_device_zero
Date: Sat, 22 Feb 2020 09:23:29 -0600 [thread overview]
Message-ID: <876b2b2c-7e16-8ae5-eb33-648b892a7274@sandeen.net> (raw)
In-Reply-To: <20200222072410.GJ9506@magnolia>
On 2/22/20 1:24 AM, Darrick J. Wong wrote:
> On Fri, Feb 21, 2020 at 09:22:12PM -0600, Eric Sandeen wrote:
>> I had a request from someone who cared about mkfs speed(!)
>> over a slower network block device to look into using faster
>> zeroing methods, particularly for the log, during mkfs.
>>
>> Using FALLOC_FL_ZERO_RANGE is faster in this case than writing
>> a bunch of zeros across a wire.
>>
>> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>> ---
>>
>> V2: Clean up all the nasty stuff I'd flung out there as a wild first
>> cut, thanks Dave.
>>
>> V3: make len_bytes a size_t; leave "end_offset" where it is for the loop
>> use. It's a bit odd but ... just don't mess with it for now, one patch
>> one change.
>>
>> diff --git a/include/builddefs.in b/include/builddefs.in
>> index 4700b527..1dd27f76 100644
>> --- a/include/builddefs.in
>> +++ b/include/builddefs.in
>> @@ -144,6 +144,9 @@ endif
>> ifeq ($(HAVE_GETFSMAP),yes)
>> PCFLAGS+= -DHAVE_GETFSMAP
>> endif
>> +ifeq ($(HAVE_FALLOCATE),yes)
>> +PCFLAGS += -DHAVE_FALLOCATE
>> +endif
>>
>> LIBICU_LIBS = @libicu_LIBS@
>> LIBICU_CFLAGS = @libicu_CFLAGS@
>> diff --git a/include/linux.h b/include/linux.h
>> index 8f3c32b0..8d5c4584 100644
>> --- a/include/linux.h
>> +++ b/include/linux.h
>> @@ -20,6 +20,10 @@
>> #include <stdio.h>
>> #include <asm/types.h>
>> #include <mntent.h>
>> +#include <fcntl.h>
>> +#if defined(HAVE_FALLOCATE)
>> +#include <linux/falloc.h>
>> +#endif
>> #ifdef OVERRIDE_SYSTEM_FSXATTR
>> # define fsxattr sys_fsxattr
>> #endif
>> @@ -164,6 +168,24 @@ static inline void platform_mntent_close(struct mntent_cursor * cursor)
>> endmntent(cursor->mtabp);
>> }
>>
>> +#if defined(FALLOC_FL_ZERO_RANGE)
>> +static inline int
>> +platform_zero_range(
>> + int fd,
>> + xfs_off_t start,
>> + size_t len)
>
> Seems fine to me, though it's unfortunate to cap this at u32.
Hm well I suppose could/should expand it. This starts out via libxfs_device_zero
as a uint "len" in sectors so it could/should be a bit bigger.
>> +{
>> + int ret;
>> +
>> + ret = fallocate(fd, FALLOC_FL_ZERO_RANGE, start, len);
>> + if (!ret)
>> + return 0;
>> + return -errno;
>> +}
>> +#else
>> +#define platform_zero_range(fd, s, l) (-EOPNOTSUP)
>
> EOPNOTSUPP (two P's)
Weird not sure how I picked that, though they are equivalent today.
*sigh* V4 I guess.
next prev parent reply other threads:[~2020-02-22 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 21:12 [PATCH, RFC] libxfs: use FALLOC_FL_ZERO_RANGE in libxfs_device_zero Eric Sandeen
2020-02-13 23:48 ` Dave Chinner
2020-02-13 23:57 ` Eric Sandeen
2020-02-14 0:25 ` Dave Chinner
2020-02-14 1:05 ` [PATCH V2] " Eric Sandeen
2020-02-14 1:34 ` Dave Chinner
2020-02-14 1:43 ` Eric Sandeen
2020-02-22 3:22 ` [PATCH V3] " Eric Sandeen
2020-02-22 7:24 ` Darrick J. Wong
2020-02-22 15:23 ` Eric Sandeen [this message]
2020-02-25 18:13 ` [PATCH V4] " Eric Sandeen
2020-02-25 18:46 ` Christoph Hellwig
2020-02-25 19:16 ` Darrick J. Wong
2020-02-25 23:33 ` Eric Sandeen
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=876b2b2c-7e16-8ae5-eb33-648b892a7274@sandeen.net \
--to=sandeen@sandeen.net \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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).