From: Christoph Hellwig <hch@infradead.org>
To: Eunhee Rho <eunhee83.rho@samsung.com>
Cc: "jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"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] [PATCH v0] f2fs: allow direct read for zoned device
Date: Fri, 29 Jul 2022 06:26:56 -0700 [thread overview]
Message-ID: <YuPgIByYgc6WSPDE@infradead.org> (raw)
In-Reply-To: <20220729002517epcms2p35eed262c3349287436c1848ab350c2d4@epcms2p3>
On Fri, Jul 29, 2022 at 09:25:17AM +0900, Eunhee Rho wrote:
> For zoned devices, f2fs forbids direct IO and forces buffered IO
> to serialize write IOs. However, the constraint does not apply to
> read IOs.
Asymetric capabilitis will cause a whole lot of problems for us. Can
we figure out why direct writes to zoned devices are not supported and
just fix that instead?
_______________________________________________
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:[~2022-07-29 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220729002517epcms2p35eed262c3349287436c1848ab350c2d4@epcms2p3>
2022-07-29 0:25 ` [f2fs-dev] [PATCH v0] f2fs: allow direct read for zoned device Eunhee Rho
2022-07-29 13:26 ` Christoph Hellwig [this message]
2022-07-31 1:22 ` Jaegeuk Kim
[not found] ` <CGME20220729002517epcms2p35eed262c3349287436c1848ab350c2d4@epcms2p8>
2022-08-01 4:06 ` Eunhee Rho
[not found] ` <CGME20220729002517epcms2p35eed262c3349287436c1848ab350c2d4@epcms2p5>
2022-08-01 4:40 ` [f2fs-dev] [PATCH v1] f2fs: remove device type check for direct IO Eunhee Rho
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=YuPgIByYgc6WSPDE@infradead.org \
--to=hch@infradead.org \
--cc=eunhee83.rho@samsung.com \
--cc=jaegeuk@kernel.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 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).