All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Hans Holmberg <hans.holmberg@wdc.com>, Chao Yu <chao@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net, damien.lemoal@wdc.com,
	aravind.ramesh@wdc.com, hans@owltronix.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] f2fs: preserve direct write semantics when buffering is forced
Date: Thu, 23 Mar 2023 15:14:59 -0700	[thread overview]
Message-ID: <ZBzPYwcoLXkFngz8@google.com> (raw)
In-Reply-To: <ZBhisCo7gTitmKeO@infradead.org>

On 03/20, Christoph Hellwig wrote:
> On Mon, Feb 20, 2023 at 01:20:04PM +0100, Hans Holmberg wrote:
> > A) Supporting proper direct writes for zoned block devices would
> > be the best, but it is currently not supported (probably for
> > a good but non-obvious reason). Would it be feasible to
> > implement proper direct IO?
> 
> I don't think why not.  In many ways direct writes to zoned devices
> should be easier than non-direct writes.
> 
> Any comments from the maintainers why the direct I/O writes to zoned
> devices are disabled?  I could not find anything helpful in the comments
> or commit logs.

The direct IO wants to overwrite the data on the same block address, while
zoned device does not support it?

WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: damien.lemoal@wdc.com, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [RFC PATCH] f2fs: preserve direct write semantics when buffering is forced
Date: Thu, 23 Mar 2023 15:14:59 -0700	[thread overview]
Message-ID: <ZBzPYwcoLXkFngz8@google.com> (raw)
In-Reply-To: <ZBhisCo7gTitmKeO@infradead.org>

On 03/20, Christoph Hellwig wrote:
> On Mon, Feb 20, 2023 at 01:20:04PM +0100, Hans Holmberg wrote:
> > A) Supporting proper direct writes for zoned block devices would
> > be the best, but it is currently not supported (probably for
> > a good but non-obvious reason). Would it be feasible to
> > implement proper direct IO?
> 
> I don't think why not.  In many ways direct writes to zoned devices
> should be easier than non-direct writes.
> 
> Any comments from the maintainers why the direct I/O writes to zoned
> devices are disabled?  I could not find anything helpful in the comments
> or commit logs.

The direct IO wants to overwrite the data on the same block address, while
zoned device does not support it?


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2023-03-23 22:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 12:20 [RFC PATCH] f2fs: preserve direct write semantics when buffering is forced Hans Holmberg
2023-02-20 12:20 ` [f2fs-dev] " Hans Holmberg via Linux-f2fs-devel
     [not found] ` <CGME20230220123747epcas2p4c72ace14d10031df7aa116999ad5fe25@epcms2p8>
2023-02-22 11:08   ` Yonggil Song
2023-02-22 11:08     ` Yonggil Song
2023-03-20 13:42 ` Christoph Hellwig
2023-03-20 13:42   ` [f2fs-dev] " Christoph Hellwig
2023-03-23 22:14   ` Jaegeuk Kim [this message]
2023-03-23 22:14     ` Jaegeuk Kim
2023-03-23 23:02     ` Damien Le Moal
2023-03-23 23:02       ` [f2fs-dev] " Damien Le Moal via Linux-f2fs-devel
2023-03-23 23:46       ` Jaegeuk Kim
2023-03-23 23:46         ` [f2fs-dev] " Jaegeuk Kim
2023-03-24  0:06         ` Damien Le Moal
2023-03-24  0:06           ` [f2fs-dev] " Damien Le Moal via Linux-f2fs-devel
2023-03-24  0:46           ` Jaegeuk Kim
2023-03-24  0:46             ` [f2fs-dev] " Jaegeuk Kim
2023-03-26 23:39             ` hch
2023-03-26 23:39               ` [f2fs-dev] " hch
2023-06-05 11:56               ` Hans Holmberg
2023-06-05 11:56                 ` [f2fs-dev] " Hans Holmberg via Linux-f2fs-devel
2023-06-05 19:36                 ` Jaegeuk Kim
2023-06-05 19:36                   ` [f2fs-dev] " Jaegeuk Kim
2023-03-23 22:37 ` Jaegeuk Kim
2023-03-23 22:37   ` [f2fs-dev] " Jaegeuk Kim

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=ZBzPYwcoLXkFngz8@google.com \
    --to=jaegeuk@kernel.org \
    --cc=aravind.ramesh@wdc.com \
    --cc=chao@kernel.org \
    --cc=damien.lemoal@wdc.com \
    --cc=hans.holmberg@wdc.com \
    --cc=hans@owltronix.com \
    --cc=hch@infradead.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.