From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, 谭姝 <shu.tan@samsung.com>
Subject: RE: [f2fs-dev] [PATCH v2] f2fs: refactor bio-related operations
Date: Wed, 04 Dec 2013 17:10:43 +0900 [thread overview]
Message-ID: <1386144643.2417.148.camel@kjgkr> (raw)
In-Reply-To: <001101cef0b6$562766e0$027634a0$@samsung.com>
Hi,
> > + if (btype == META)
> > + rw |= REQ_META;
> > +
> > + if (is_read_io(rw)) {
> > + if (sync)
> > + rw |= READ_SYNC;
> > + submit_bio(rw, io->bio);
> > + trace_f2fs_submit_read_bio(sbi->sb, rw, type, io->bio);
> > + io->bio = NULL;
> > + return;
> > + }
> > +
> > + if (sync)
> > + rw |= WRITE_SYNC;
>
> rw = WRITE_SYNC; ?
No, since it removes the REQ_META.
See above.
>
> > + if (type >= META_FLUSH)
> > + rw |= WRITE_FLUSH_FUA;
>
> rw = WRITE_FLUSH_FUA; ?
>
> > +
> > + /*
> > + * META_FLUSH is only from the checkpoint procedure, and we should wait
> > + * this metadata bio for FS consistency.
> > + */
> > + if (type == META_FLUSH) {
> > + DECLARE_COMPLETION_ONSTACK(wait);
> > + io->bio->bi_private = &wait;
> > + submit_bio(rw, io->bio);
> > + wait_for_completion(&wait);
> > + } else {
> > + submit_bio(rw, io->bio);
> > + }
> > + trace_f2fs_submit_write_bio(sbi->sb, rw, btype, io->bio);
> > + io->bio = NULL;
> > +}
>
> [snip]
>
> Thanks,
> Yu
>
--
Jaegeuk Kim
Samsung
next prev parent reply other threads:[~2013-12-04 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 6:25 [PATCH] f2fs: refactor bio-related operations Jaegeuk Kim
2013-12-02 2:55 ` Gu Zheng
2013-12-02 4:47 ` Chao Yu
2013-12-02 8:24 ` [f2fs-dev] " Jaegeuk Kim
2013-12-02 8:27 ` [PATCH v2] " Jaegeuk Kim
2013-12-02 9:37 ` [f2fs-dev] " Chao Yu
2013-12-04 6:01 ` Chao Yu
2013-12-04 8:10 ` Jaegeuk Kim [this message]
2013-12-04 8:22 ` 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=1386144643.2417.148.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=chao2.yu@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shu.tan@samsung.com \
/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).