From: Phil Karn <karn@philkarn.net>
To: xfs@oss.sgi.com
Subject: fallocate everywhere?
Date: Fri, 14 Jan 2011 10:18:56 -0800 [thread overview]
Message-ID: <4D309390.4060009@philkarn.net> (raw)
Can anyone think of a good reason *not* to sprinkle fallocate() calls
through as many Linux utilities as possible? E.g., programs like rsync,
tar, cpio, pax, ftp, mv, cp -- anything and everything that creates a
file with a size known in advance.
As far as I can tell, calling fallocate() when it's not supported
quickly returns an error and does no harm. So I can't even think of a
reason to only make it optional. If it's implemented as an
off-by-default option, most people would probably not know about it so
it would rarely get used. Those who do know about it would frequently
forget to use it, and choosing and learning a separate option for every
command would be painful.
Besides xfs, ext4 supports fallocate so I expect that most Linux systems
will be able to benefit from it fairly soon.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-01-14 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 18:18 Phil Karn [this message]
2011-01-15 4:38 ` fallocate everywhere? Dave Chinner
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=4D309390.4060009@philkarn.net \
--to=karn@philkarn.net \
--cc=karn@ka9q.net \
--cc=xfs@oss.sgi.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