From: majianpeng <majianpeng@gmail.com>
To: axboe <axboe@kernel.dk>, "konrad.wilk" <konrad.wilk@oracle.com>,
"chris.mason" <chris.mason@fusionio.com>,
viro <viro@ZenIV.linux.org.uk>, tytso <tytso@mit.edu>,
"adilger.kernel" <adilger.kernel@dilger.ca>,
shaggy <shaggy@kernel.org>, mfasheh <mfasheh@suse.com>,
jlbec <jlbec@evilplan.org>, bpm <bpm@sgi.com>,
elder <elder@kernel.org>
Cc: jfs-discussion <jfs-discussion@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
xfs <xfs@oss.sgi.com>, linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
ocfs2-devel <ocfs2-devel@oss.oracle.com>
Subject: [PATCH 0/8] Set bi_rw when alloc bio before call bio_add_page.
Date: Mon, 30 Jul 2012 15:14:28 +0800 [thread overview]
Message-ID: <201207301514247032532@gmail.com> (raw)
When exec bio_alloc, the bi_rw is zero.But after calling bio_add_page,
it will use bi_rw.
Fox example, in functiion __bio_add_page,it will call merge_bvec_fn().
The merge_bvec_fn of raid456 will use the bi_rw to judge the merge.
>> if ((bvm->bi_rw & 1) == WRITE)
>> return biovec->bv_len; /* always allow writes to be mergeable */
Jianpeng Ma (8):
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
Evalue bio->bi_rw after calling bio_alloc() and before calling
bio_add_page().
block/blk-lib.c | 1 +
drivers/block/xen-blkback/blkback.c | 1 +
fs/btrfs/check-integrity.c | 1 +
fs/direct-io.c | 1 +
fs/ext4/page-io.c | 1 +
fs/jfs/jfs_metapage.c | 1 +
fs/ocfs2/cluster/heartbeat.c | 8 +++++---
fs/xfs/xfs_aops.c | 2 ++
fs/xfs/xfs_buf.c | 1 +
9 files changed, 14 insertions(+), 3 deletions(-)
--
1.7.9.5
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-07-30 7:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 7:14 majianpeng [this message]
2012-07-30 15:39 ` [PATCH 0/8] Set bi_rw when alloc bio before call bio_add_page Konrad Rzeszutek Wilk
2012-07-31 0:42 ` majianpeng
2012-07-30 21:42 ` Dave Chinner
2012-07-31 0:55 ` majianpeng
2012-07-31 1:14 ` Dave Chinner
2012-08-10 15:23 ` Muthu Kumar
2012-08-10 15:29 ` Muthu Kumar
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=201207301514247032532@gmail.com \
--to=majianpeng@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=axboe@kernel.dk \
--cc=bpm@sgi.com \
--cc=chris.mason@fusionio.com \
--cc=elder@kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlbec@evilplan.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=shaggy@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
--cc=xfs@oss.sgi.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).