From: Jeremy Fitzhardinge <jeremy@goop.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, jens.axboe@oracle.com
Subject: [PATCH 1/2] bio: define __BIOVEC_PHYS_MERGEABLE
Date: Fri, 24 Oct 2008 13:59:03 -0700 [thread overview]
Message-ID: <49023717.6070604@goop.org> (raw)
In-Reply-To: <20081024143836K.fujita.tomonori@lab.ntt.co.jp>
Define __BIOVEC_PHYS_MERGEABLE as the default implementation of
BIOVEC_PHYS_MERGEABLE, so that its available for reuse within an
arch-specific definition of BIOVEC_PHYS_MERGEABLE.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Cc: Jens Axboe <jens.axboe@oracle.com>
---
include/linux/bio.h | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
===================================================================
--- a/include/linux/bio.h
+++ b/include/linux/bio.h
@@ -221,12 +221,16 @@
#define __BVEC_END(bio) bio_iovec_idx((bio), (bio)->bi_vcnt - 1)
#define __BVEC_START(bio) bio_iovec_idx((bio), (bio)->bi_idx)
+/* Default implementation of BIOVEC_PHYS_MERGEABLE */
+#define __BIOVEC_PHYS_MERGEABLE(vec1, vec2) \
+ ((bvec_to_phys((vec1)) + (vec1)->bv_len) == bvec_to_phys((vec2)))
+
/*
* allow arch override, for eg virtualized architectures (put in asm/io.h)
*/
#ifndef BIOVEC_PHYS_MERGEABLE
#define BIOVEC_PHYS_MERGEABLE(vec1, vec2) \
- ((bvec_to_phys((vec1)) + (vec1)->bv_len) == bvec_to_phys((vec2)))
+ __BIOVEC_PHYS_MERGEABLE(vec1, vec2)
#endif
#define __BIO_SEG_BOUNDARY(addr1, addr2, mask) \
next prev parent reply other threads:[~2008-10-24 20:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 5:41 [PATCH] x86: remove dead BIO_VMERGE_BOUNDARY definition FUJITA Tomonori
2008-10-24 20:58 ` Jeremy Fitzhardinge
2008-10-27 4:42 ` FUJITA Tomonori
2008-10-24 20:59 ` Jeremy Fitzhardinge [this message]
2008-10-24 20:59 ` [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with BIOVEC_PHYS_MERGEABLE Jeremy Fitzhardinge
2008-10-27 3:52 ` FUJITA Tomonori
2008-10-27 8:21 ` Jeremy Fitzhardinge
2008-10-27 8:37 ` FUJITA Tomonori
2008-10-27 9:18 ` Jeremy Fitzhardinge
2008-10-27 9:36 ` FUJITA Tomonori
2008-10-27 9:41 ` Jens Axboe
2008-10-27 11:43 ` Jeremy Fitzhardinge
2008-10-27 11:57 ` Jens Axboe
2008-10-28 23:06 ` FUJITA Tomonori
2008-10-29 8:37 ` Ingo Molnar
2008-10-29 9:24 ` Jeremy Fitzhardinge
2008-10-29 10:51 ` Ingo Molnar
2008-10-29 11:25 ` Ingo Molnar
2008-10-29 11:27 ` Jens Axboe
2008-10-29 11:30 ` Ingo Molnar
2008-10-29 11:34 ` Jens Axboe
2008-10-29 11:55 ` FUJITA Tomonori
2008-10-29 12:12 ` Jeremy Fitzhardinge
2008-10-29 13:03 ` Ingo Molnar
2008-10-29 13:06 ` Jeremy Fitzhardinge
2008-10-29 13:06 ` Jens Axboe
2008-10-29 9:27 ` Jens Axboe
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=49023717.6070604@goop.org \
--to=jeremy@goop.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome