linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@meta.com>,
	linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
	axboe@kernel.dk, io-uring@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, joshi.k@samsung.com,
	javier.gonz@samsung.com, Nitesh Shetty <nj.shetty@samsung.com>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCHv8 1/6] block, fs: restore kiocb based write hint processing
Date: Mon, 21 Oct 2024 09:47:47 -0600	[thread overview]
Message-ID: <ZxZ3o_HzN8HN6QPK@kbusch-mbp> (raw)
In-Reply-To: <20241018055032.GB20262@lst.de>

On Fri, Oct 18, 2024 at 07:50:32AM +0200, Christoph Hellwig wrote:
> On Thu, Oct 17, 2024 at 09:09:32AM -0700, Keith Busch wrote:
> >  {
> >  	*kiocb = (struct kiocb) {
> >  		.ki_filp = filp,
> >  		.ki_flags = filp->f_iocb_flags,
> >  		.ki_ioprio = get_current_ioprio(),
> > +		.ki_write_hint = file_write_hint(filp),
> 
> And we'll need to distinguish between the per-inode and per file
> hint.  I.e. don't blindly initialize ki_write_hint to the per-inode
> one here, but make that conditional in the file operation.

Maybe someone wants to do direct-io with partions where each partition
has a different default "hint" when not provided a per-io hint? I don't
know of such a case, but it doesn't sound terrible. In any case, I feel
if you're directing writes through these interfaces, you get to keep all
the pieces: user space controls policy, kernel just provides the
mechanisms to do it.

  reply	other threads:[~2024-10-21 15:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 16:09 [PATCHv8 0/6] write hints for nvme fdp Keith Busch
2024-10-17 16:09 ` [PATCHv8 2/6] block: use generic u16 for write hints Keith Busch
2024-10-18  5:46   ` Christoph Hellwig
2024-10-24 19:45     ` Keith Busch
2024-10-25 12:20       ` Christoph Hellwig
2024-10-18  6:00   ` Hannes Reinecke
2024-10-18 16:12   ` Bart Van Assche
2024-10-21 15:03     ` Keith Busch
2024-10-17 16:09 ` [PATCHv8 3/6] block: introduce max_write_hints queue limit Keith Busch
2024-10-18  5:51   ` Christoph Hellwig
2024-10-18  6:01   ` Hannes Reinecke
2024-10-18 16:18   ` Bart Van Assche
2024-10-21 15:02     ` Keith Busch
2024-10-17 16:09 ` [PATCHv8 4/6] fs: introduce per-io hint support flag Keith Busch
2024-10-18  5:52   ` Christoph Hellwig
2024-10-18  6:03   ` Hannes Reinecke
2024-10-17 16:09 ` [PATCHv8 5/6] io_uring: enable per-io hinting capability Keith Busch
2024-10-18  5:53   ` Christoph Hellwig
2024-10-18  6:03   ` Hannes Reinecke
     [not found] ` <CGME20241017161628epcas5p1006f392dc6c208634997f3a950ec8c67@epcas5p1.samsung.com>
     [not found]   ` <20241017160937.2283225-7-kbusch@meta.com>
2024-10-18 10:48     ` [PATCHv8 6/6] nvme: enable FDP support Kanchan Joshi
2024-10-21 15:08       ` Keith Busch
     [not found] ` <20241017160937.2283225-2-kbusch@meta.com>
2024-10-18  5:50   ` [PATCHv8 1/6] block, fs: restore kiocb based write hint processing Christoph Hellwig
2024-10-21 15:47     ` Keith Busch [this message]
2024-10-21 17:09       ` Bart Van Assche
2024-10-21 19:35         ` Keith Busch
2024-10-22  6:43       ` Christoph Hellwig
2024-10-22 14:37         ` Keith Busch
2024-10-22 14:40           ` Christoph Hellwig
2024-10-18 16:11   ` Bart Van Assche

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=ZxZ3o_HzN8HN6QPK@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=io-uring@vger.kernel.org \
    --cc=javier.gonz@samsung.com \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@meta.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nj.shetty@samsung.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).