linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: jeremy@goop.org, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with BIOVEC_PHYS_MERGEABLE
Date: Wed, 29 Oct 2008 10:27:34 +0100	[thread overview]
Message-ID: <20081029092733.GS22217@kernel.dk> (raw)
In-Reply-To: <20081029080603J.fujita.tomonori@lab.ntt.co.jp>

On Wed, Oct 29 2008, FUJITA Tomonori wrote:
> On Mon, 27 Oct 2008 12:57:00 +0100
> Jens Axboe <jens.axboe@oracle.com> wrote:
> 
> > On Mon, Oct 27 2008, Jeremy Fitzhardinge wrote:
> > > Jens Axboe wrote:
> > > >Pretty much baffles me as well, xen should just need to do
> > > >
> > > >#define BIOVEC_PHYS_MERGEABLE(vec1, vec2)       0
> > > >  
> > > 
> > > It needs to be a runtime switch, since we only want to do this when 
> > > actually running under Xen.  Also, its possible that the two pages might 
> > > actually be physically contiguous, so they could be merged anyway.
> > 
> > Alright, then add a xen_biovec_phys_mergeable(vec1, vec2) in the xen
> > code that actually checks this for real. You can add your switch there
> > as well. Then put the BIOVEC_PHYS_MERGEABLE() in the xen arch includes,
> > done.
> > 
> > What Tomo is saying is that this has nothing to do with virtual merging,
> > and he's right.
> 
> Yeah, overriding BIOVEC_PHYS_MERGEABLE perfectly works for Xen. And it
> is not related with BIO_VMERGE_BOUNDARY at all.
> 
> Ingo, please put this patch into your tree:
> 
> http://marc.info/?l=linux-kernel&m=122482703716620&w=2

You can add my Signed-off-by: as well.

-- 
Jens Axboe


      parent reply	other threads:[~2008-10-29  9:28 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 ` [PATCH 1/2] bio: define __BIOVEC_PHYS_MERGEABLE Jeremy Fitzhardinge
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 [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=20081029092733.GS22217@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jeremy@goop.org \
    --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;
as well as URLs for NNTP newsgroup(s).