From: Paul Eggert <eggert@cs.ucla.edu>
To: Christoph Hellwig <hch@lst.de>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
libc-alpha@sourceware.org, linux-fsdevel@vger.kernel.org
Subject: Re: posix_fallocate behavior in glibc
Date: Mon, 29 Jul 2024 10:23:09 -0700 [thread overview]
Message-ID: <91e405eb-0f55-4ffc-a01d-660e2e5d0b84@cs.ucla.edu> (raw)
In-Reply-To: <20240729160951.GA30183@lst.de>
On 2024-07-29 09:09, Christoph Hellwig wrote:
> How can we get rid of this glibc fallback that turns the implementations
> non-conformant and increases write amplication for no good reason?
The simplest solution would be to remove the broken fallback in glibc. A
more conservative possibility would be to use the fallback only on file
system types that lack native fallocate and where the fallback is known
to work (which are they?). Perhaps you could propose a patch along
either line.
next prev parent reply other threads:[~2024-07-29 17:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 16:09 posix_fallocate behavior in glibc Christoph Hellwig
2024-07-29 17:23 ` Paul Eggert [this message]
2024-07-29 17:43 ` Christoph Hellwig
2024-07-29 17:54 ` Adhemerval Zanella Netto
[not found] ` <CAPBLoAf11hM0PLhqPG5gUyivU9U1manpOOhDWCPugUmWc1VVUw@mail.gmail.com>
2024-07-29 18:45 ` Christoph Hellwig
2024-07-29 17:57 ` Florian Weimer
2024-07-29 18:44 ` Christoph Hellwig
2024-07-29 18:52 ` Florian Weimer
2024-07-29 19:01 ` Christoph Hellwig
2024-07-29 19:23 ` Florian Weimer
2024-07-30 15:47 ` Christoph Hellwig
2024-07-30 16:11 ` Paul Eggert
2024-07-30 16:20 ` Christoph Hellwig
2024-07-30 17:03 ` Florian Weimer
2024-07-30 17:08 ` Christoph Hellwig
2024-07-30 17:29 ` Florian Weimer
2024-07-30 17:52 ` Mark Wielaard
2024-07-31 2:32 ` Theodore Ts'o
2024-07-29 23:53 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2024-06-26 6:01 Christoph Hellwig
2024-07-29 15:09 ` Christoph Hellwig
2024-07-29 15:11 ` Sam James
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=91e405eb-0f55-4ffc-a01d-660e2e5d0b84@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=hch@lst.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trondmy@hammerspace.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).