From: Damien Le Moal via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: "jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"hch@infradead.org" <hch@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<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 23:02:12 +0000 [thread overview]
Message-ID: <402cc90ce5defa81c937c3fcd09de1f6497459ee.camel@wdc.com> (raw)
In-Reply-To: <ZBzPYwcoLXkFngz8@google.com>
On Thu, 2023-03-23 at 15:14 -0700, Jaegeuk Kim wrote:
> 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?
Surely that is not the case with LFS mode, doesn't it ? Otherwise, even
buffered overwrites would have an issue.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-03-23 23:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 12:20 [f2fs-dev] [RFC PATCH] f2fs: preserve direct write semantics when buffering is forced Hans Holmberg via Linux-f2fs-devel
[not found] ` <CGME20230220123747epcas2p4c72ace14d10031df7aa116999ad5fe25@epcms2p8>
2023-02-22 11:08 ` Yonggil Song
2023-03-20 13:42 ` Christoph Hellwig
2023-03-23 22:14 ` Jaegeuk Kim
2023-03-23 23:02 ` Damien Le Moal via Linux-f2fs-devel [this message]
2023-03-23 23:46 ` Jaegeuk Kim
2023-03-24 0:06 ` Damien Le Moal via Linux-f2fs-devel
2023-03-24 0:46 ` Jaegeuk Kim
2023-03-26 23:39 ` hch
2023-06-05 11:56 ` Hans Holmberg via Linux-f2fs-devel
2023-06-05 19:36 ` Jaegeuk Kim
2023-03-23 22:37 ` 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=402cc90ce5defa81c937c3fcd09de1f6497459ee.camel@wdc.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=Damien.LeMoal@wdc.com \
--cc=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--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 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).