From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Avi Kivity <avi@scylladb.com>, Eric Sandeen <sandeen@sandeen.net>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
linux-xfs@vger.kernel.org
Subject: Re: agcount for 2TB, 4TB and 8TB drives
Date: Wed, 18 Oct 2017 00:31:04 -0700 [thread overview]
Message-ID: <20171018073104.GA6274@infradead.org> (raw)
In-Reply-To: <20171015220018.GG3666@dastard>
On Mon, Oct 16, 2017 at 09:00:19AM +1100, Dave Chinner wrote:
> fallocate will block *all* IO and mmap faults on that file, not just
> the ones that require allocation. fallocate creates a complete IO
> submission pipeline stall, punting all new IO submissions to the
> background worker where they will block until fallocate completes.
Not sure if it helps Avis case, but I think we could relax the
fallocate exclusive i_rwsem requirement a bit, similar to direct I/O
writes. Basically as long as your fallocate is block aligned we
should be fine with a shared iolock for the "normal" allocating
fallocate (discounting things like hole punches and extent shifts
of course).
prev parent reply other threads:[~2017-10-18 7:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 8:46 agcount for 2TB, 4TB and 8TB drives Gandalf Corvotempesta
2017-10-06 15:38 ` Darrick J. Wong
2017-10-06 16:18 ` Eric Sandeen
2017-10-06 22:20 ` Dave Chinner
2017-10-06 22:21 ` Eric Sandeen
2017-10-09 8:05 ` Avi Kivity
2017-10-09 11:23 ` Dave Chinner
2017-10-09 15:46 ` Avi Kivity
2017-10-09 22:03 ` Dave Chinner
2017-10-10 9:07 ` Avi Kivity
2017-10-10 22:55 ` Dave Chinner
2017-10-13 8:13 ` Avi Kivity
2017-10-14 22:42 ` Dave Chinner
2017-10-15 9:36 ` Avi Kivity
2017-10-15 22:00 ` Dave Chinner
2017-10-16 10:00 ` Avi Kivity
2017-10-16 22:31 ` Dave Chinner
2017-10-18 7:31 ` Christoph Hellwig [this message]
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=20171018073104.GA6274@infradead.org \
--to=hch@infradead.org \
--cc=avi@scylladb.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=gandalf.corvotempesta@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).