Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Pranjal Shrivastava <praan@google.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Matthew Wilcox <willy@infradead.org>,
	Trond Myklebust <trondmy@kernel.org>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Anna Schumaker <anna@kernel.org>,
	Shivaji Kant <shivajikant@google.com>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 6/7] nfs: Optimize direct I/O to use folios for requests
Date: Fri, 3 Jul 2026 07:00:35 -0700	[thread overview]
Message-ID: <akfAgy52s_Gch2KG@infradead.org> (raw)
In-Reply-To: <akevQfFVteCOD6LM@google.com>

On Fri, Jul 03, 2026 at 12:46:58PM +0000, Pranjal Shrivastava wrote:
> Do we have use-cases for a kernel user for direct I/O ? (Just curious to
> know if there's something on the horizon).

Plenty.  Basically any storage on file driver, or storage / file system
server:  loop, zloop, nvmet, scsi target and nfsd ar the ones I know off
by head.



      reply	other threads:[~2026-07-03 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260616134000.2733403-1-praan@google.com>
     [not found] ` <20260616134000.2733403-7-praan@google.com>
     [not found]   ` <7ee3bcfdd6126c93cbb1c219bf601182b95c10d9.camel@kernel.org>
     [not found]     ` <ajGGpDvzZdkGtSbN@google.com>
2026-06-18 14:10       ` [PATCH v2 6/7] nfs: Optimize direct I/O to use folios for requests Christoph Hellwig
2026-06-18 18:20         ` Matthew Wilcox
2026-06-19 12:32           ` Pranjal Shrivastava
2026-06-26  6:56           ` Christoph Hellwig
2026-07-03 12:46             ` Pranjal Shrivastava
2026-07-03 14:00               ` 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=akfAgy52s_Gch2KG@infradead.org \
    --to=hch@infradead.org \
    --cc=anna@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=praan@google.com \
    --cc=shivajikant@google.com \
    --cc=trondmy@kernel.org \
    --cc=willy@infradead.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