linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: [GIT PULL] zonefs changes for 6.5-rc1
Date: Mon, 26 Jun 2023 21:51:45 +0900	[thread overview]
Message-ID: <20230626125145.1865163-1-dlemoal@kernel.org> (raw)

From: Damien Le Moal <damien.lemoal@opensource.wdc.com>

Linus,

The following changes since commit 9561de3a55bed6bdd44a12820ba81ec416e705a7:

  Linux 6.4-rc5 (2023-06-04 14:04:27 -0400)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs tags/zonefs-6.5-rc1

for you to fetch changes up to 8812387d056957355ef1d026cd38bed3830649db:

  zonefs: set FMODE_CAN_ODIRECT instead of a dummy direct_IO method (2023-06-14 08:51:18 +0900)

----------------------------------------------------------------
zonefs changes for 6.5

 - Modify the synchronous direct write path to use iomap instead of
   manually coding issuing zone append write BIOs, from me.

 - Use the FMODE_CAN_ODIRECT file flag to indicate support from direct
   IO instead of using the old way with noop direct_io methods, from
   Christoph.

----------------------------------------------------------------
Christoph Hellwig (1):
      zonefs: set FMODE_CAN_ODIRECT instead of a dummy direct_IO method

Damien Le Moal (1):
      zonefs: use iomap for synchronous direct writes

 fs/zonefs/file.c   | 208 ++++++++++++++++++++++++++++-------------------------
 fs/zonefs/super.c  |   9 ++-
 fs/zonefs/zonefs.h |   2 +
 3 files changed, 121 insertions(+), 98 deletions(-)

             reply	other threads:[~2023-06-26 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 12:51 Damien Le Moal [this message]
2023-06-26 20:02 ` [GIT PULL] zonefs changes for 6.5-rc1 pr-tracker-bot

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=20230626125145.1865163-1-dlemoal@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).