From: Christoph Hellwig <hch@lst.de>
To: linux-xfs@vger.kernel.org
Cc: agruenba@redhat.com
Subject: simplify the Q_GETNEXTQUOTA implementation
Date: Tue, 20 Jun 2017 11:02:42 +0200 [thread overview]
Message-ID: <20170620090244.30876-1-hch@lst.de> (raw)
Hi all,
the first patch simplifieѕ xfs_dq_get_next_id to use raw extent
list lookups instead of using the SEEK_DATA code. This should make
it a bit more efficient and doesn't require the new iomap based
SEEK_HOLE/DATA code to support this special use case. Note that
I've not removed various now unused bits of the lseek code to reduce
the conflicts with Andreas' work.
The second one just removes a whitespace only line I noticed while
looking at the history of the code.
next reply other threads:[~2017-06-20 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 9:02 Christoph Hellwig [this message]
2017-06-20 9:02 ` [PATCH 1/2] xfs: rewrite xfs_dq_get_next_id using xfs_iext_lookup_extent Christoph Hellwig
2017-06-20 19:51 ` Darrick J. Wong
2017-06-20 20:17 ` Eric Sandeen
2017-06-20 20:31 ` Christoph Hellwig
2017-06-20 9:02 ` [PATCH 2/2] xfs: remove a whitespace-only line from xfs_fs_get_nextdqblk Christoph Hellwig
2017-06-20 20:20 ` 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=20170620090244.30876-1-hch@lst.de \
--to=hch@lst.de \
--cc=agruenba@redhat.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).