From: Chao Yu <chao.yu@oppo.com>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs-tools: add atomic write related options to f2fs_io write command
Date: Tue, 8 Feb 2022 11:03:24 +0800 [thread overview]
Message-ID: <d1d46df7-e761-5086-571f-d35bba2f8e69@oppo.com> (raw)
In-Reply-To: <20220202201727.3410310-1-daeho43@gmail.com>
On 2022/2/3 4:17, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Added two option to f2fs_io "write" command.
> - atomic_commit : atomic write & commit
> - atomic_abort : atomic write & abort
> Also, added an optional option {delay}, which is in ms unit and optional
> only for atomic_commit and atomic_abort.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2022-02-08 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 20:17 [PATCH] f2fs-tools: add atomic write related options to f2fs_io write command Daeho Jeong
2022-02-08 3:03 ` Chao Yu [this message]
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=d1d46df7-e761-5086-571f-d35bba2f8e69@oppo.com \
--to=chao.yu@oppo.com \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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