From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jens Axboe <axboe@kernel.dk>, jaegeuk@kernel.org
Cc: Qi Han <hanqi@vivo.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to return -EOPNOTSUPP for uncached write
Date: Wed, 6 Aug 2025 09:51:21 +0800 [thread overview]
Message-ID: <9c7ef111-548c-4751-af9f-335563bda263@kernel.org> (raw)
In-Reply-To: <587aaee2-8d84-4eb5-9b87-22947abd0752@kernel.dk>
On 8/5/25 23:37, Jens Axboe wrote:
> On 8/5/25 12:19 AM, Chao Yu wrote:
>> f2fs doesn't support uncached write yet, for write() w/ IOCB_DONTCACHE
>> flag, let's return -EOPNOTSUPP instead of ignoring IOCB_DONTCACHE flag
>> and write w/o uncached IO.
>
> Didn't we agree that write support should be pursued first before
> bifurcating the read/write DONTCACHE support?
Yeah, no worries, this is just used for test purpose, will drop this once
Qi Han prepare the new patchset supporting dontcache in both read and write
path. :)
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Jens Axboe <axboe@kernel.dk>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Qi Han <hanqi@vivo.com>
Subject: Re: [PATCH v2] f2fs: fix to return -EOPNOTSUPP for uncached write
Date: Wed, 6 Aug 2025 09:51:21 +0800 [thread overview]
Message-ID: <9c7ef111-548c-4751-af9f-335563bda263@kernel.org> (raw)
In-Reply-To: <587aaee2-8d84-4eb5-9b87-22947abd0752@kernel.dk>
On 8/5/25 23:37, Jens Axboe wrote:
> On 8/5/25 12:19 AM, Chao Yu wrote:
>> f2fs doesn't support uncached write yet, for write() w/ IOCB_DONTCACHE
>> flag, let's return -EOPNOTSUPP instead of ignoring IOCB_DONTCACHE flag
>> and write w/o uncached IO.
>
> Didn't we agree that write support should be pursued first before
> bifurcating the read/write DONTCACHE support?
Yeah, no worries, this is just used for test purpose, will drop this once
Qi Han prepare the new patchset supporting dontcache in both read and write
path. :)
Thanks,
next prev parent reply other threads:[~2025-08-06 1:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 6:19 [f2fs-dev] [PATCH v2] f2fs: fix to return -EOPNOTSUPP for uncached write Chao Yu via Linux-f2fs-devel
2025-08-05 6:19 ` Chao Yu
2025-08-05 15:37 ` [f2fs-dev] " Jens Axboe
2025-08-05 15:37 ` Jens Axboe
2025-08-06 1:51 ` Chao Yu via Linux-f2fs-devel [this message]
2025-08-06 1:51 ` Chao Yu
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=9c7ef111-548c-4751-af9f-335563bda263@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=axboe@kernel.dk \
--cc=chao@kernel.org \
--cc=hanqi@vivo.com \
--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 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.