From: Christoph Hellwig <hch@lst.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fs: remove fs.f_write_hint
Date: Mon, 14 Mar 2022 09:02:09 +0100 [thread overview]
Message-ID: <20220314080209.GC4921@lst.de> (raw)
In-Reply-To: <Yi1Dc0x9j5bPAlQz@zeniv-ca.linux.org.uk>
On Sun, Mar 13, 2022 at 01:05:55AM +0000, Al Viro wrote:
> On Mon, Mar 07, 2022 at 11:47:01AM +0100, Christoph Hellwig wrote:
> > The value is now completely unused except for reporting it back through
> > the F_GET_FILE_RW_HINT ioctl, so remove the value and the two ioctls
> > for it.
>
> Obvious question - which userland code issues these ioctls? I obviously
> like the series, but...
The only places I've ever found are fio and ceph. Despite all the noise
about Android, the google code search for Android does not actually find
a user there.
next prev parent reply other threads:[~2022-03-14 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 10:46 remove write hint leftovers Christoph Hellwig
2022-03-07 10:47 ` [PATCH 1/2] fs: remove kiocb.ki_hint Christoph Hellwig
2022-03-07 10:47 ` [PATCH 2/2] fs: remove fs.f_write_hint Christoph Hellwig
2022-03-07 13:52 ` Jens Axboe
2022-03-13 1:05 ` Al Viro
2022-03-14 8:02 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-08 6:05 remove write hint leftovers v2 Christoph Hellwig
2022-03-08 6:05 ` [PATCH 2/2] fs: remove fs.f_write_hint Christoph Hellwig
2022-03-08 22:20 ` Chaitanya Kulkarni
2022-03-08 23:11 ` 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=20220314080209.GC4921@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).