From: Christoph Hellwig <hch@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 5/5] f2fs: use blk_plug in all the possible paths
Date: Thu, 14 Jul 2016 19:21:32 -0700 [thread overview]
Message-ID: <20160715022132.GA1513@infradead.org> (raw)
In-Reply-To: <20160715004629.43143-5-jaegeuk@kernel.org>
On Thu, Jul 14, 2016 at 05:46:29PM -0700, Jaegeuk Kim wrote:
> The main reason is that blk_start_plug can be used to wake up from low-power
> mode before submitting further bios.
Where does that myth come from?
next prev parent reply other threads:[~2016-07-15 2:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 0:46 [PATCH 1/5] f2fs: refactor __exchange_data_block for speed up Jaegeuk Kim
2016-07-15 0:46 ` [PATCH 2/5] f2fs: disable extent_cache for fcollapse/finsert inodes Jaegeuk Kim
2016-07-15 0:46 ` [PATCH 3/5] f2fs: support copy_file_range Jaegeuk Kim
2016-07-15 0:46 ` [PATCH 4/5] f2fs: add maximum prefree segments Jaegeuk Kim
2016-07-15 0:46 ` [PATCH 5/5] f2fs: use blk_plug in all the possible paths Jaegeuk Kim
2016-07-15 2:21 ` Christoph Hellwig [this message]
2016-07-15 3:05 ` Jaegeuk Kim
2016-07-19 3:59 ` Christoph Hellwig
2016-07-19 5:49 ` 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=20160715022132.GA1513@infradead.org \
--to=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.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