All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Joe Thornber <joe@fib011235813.fsnet.co.uk>
Cc: Austin Gonyou <austin@coremetrics.com>,
	linux-lvm@sistina.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-lvm] Re: [PATCH] 2.5 version of device mapper submission
Date: Tue Oct 15 04:59:21 2002	[thread overview]
Message-ID: <20021015093608.GF5294@suse.de> (raw)
In-Reply-To: <20021015093244.GA3782@fib011235813.fsnet.co.uk>

On Tue, Oct 15 2002, Joe Thornber wrote:
> On Tue, Oct 15, 2002 at 10:21:52AM +0200, Jens Axboe wrote:
> > On Mon, Oct 14 2002, Joe Thornber wrote:
> > > 10.patch
> > >   [Device-mapper]
> > >   Add call to blk_queue_bounce() at the beginning of the request function.
> > 
> > What on earth for? I also see that you are setting BLK_BOUNCE_HIGH as
> > the bounce limit unconditionally for your queue. Puzzled.
> 
> This is just me stupidly copying loop.c, already found out it doesn't
> work.  Please ignore.

Well it should work, but dm never ever wants to bounce any data on its
own. That should only happen at the target queue, if at all.

> > When does dm even have to touch the data in the bio?
> 
> Tell me; if I'm splitting a bio using bio_clone, and then map the bio
> to a driver that calls blk_queue_bounce.  How can I avoid the
> 
>         BUG_ON((*bio_orig)->bi_idx);
> 
> triggering ?  Or is bio_clone not to be used anymore ?

(btw, do you have a complete patch against a recent kernel?)

Bouncing has just never been used with a cloned bio, so there might be a
corner case or two that needs to be fixed up. But walk me through your
request handling, please. It seems you are always allocating a
clone_info and bio clone for io?

-- 
Jens Axboe

WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@suse.de>
To: Joe Thornber <joe@fib011235813.fsnet.co.uk>
Cc: Austin Gonyou <austin@coremetrics.com>,
	linux-lvm@sistina.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-lvm] Re: [PATCH] 2.5 version of device mapper submission
Date: Tue, 15 Oct 2002 11:36:08 +0200	[thread overview]
Message-ID: <20021015093608.GF5294@suse.de> (raw)
In-Reply-To: <20021015093244.GA3782@fib011235813.fsnet.co.uk>

On Tue, Oct 15 2002, Joe Thornber wrote:
> On Tue, Oct 15, 2002 at 10:21:52AM +0200, Jens Axboe wrote:
> > On Mon, Oct 14 2002, Joe Thornber wrote:
> > > 10.patch
> > >   [Device-mapper]
> > >   Add call to blk_queue_bounce() at the beginning of the request function.
> > 
> > What on earth for? I also see that you are setting BLK_BOUNCE_HIGH as
> > the bounce limit unconditionally for your queue. Puzzled.
> 
> This is just me stupidly copying loop.c, already found out it doesn't
> work.  Please ignore.

Well it should work, but dm never ever wants to bounce any data on its
own. That should only happen at the target queue, if at all.

> > When does dm even have to touch the data in the bio?
> 
> Tell me; if I'm splitting a bio using bio_clone, and then map the bio
> to a driver that calls blk_queue_bounce.  How can I avoid the
> 
>         BUG_ON((*bio_orig)->bi_idx);
> 
> triggering ?  Or is bio_clone not to be used anymore ?

(btw, do you have a complete patch against a recent kernel?)

Bouncing has just never been used with a cloned bio, so there might be a
corner case or two that needs to be fixed up. But walk me through your
request handling, please. It seems you are always allocating a
clone_info and bio clone for io?

-- 
Jens Axboe


  reply	other threads:[~2002-10-15  4:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 13:13 [linux-lvm] [PATCH] 2.5 version of device mapper submission Joe Thornber
2002-10-09 18:12 ` Joe Thornber
2002-10-09 13:32 ` [linux-lvm] " Andrew Morton
2002-10-09 18:31   ` Andrew Morton
2002-10-09 14:23   ` [linux-lvm] " Joe Thornber
2002-10-09 18:44     ` Joe Thornber
2002-10-12 14:56 ` [linux-lvm] " Alan Cox
2002-10-12 20:05   ` Alan Cox
2002-10-12 15:09   ` [linux-lvm] " Alan Cox
2002-10-12 20:19     ` Alan Cox
2002-10-14 12:05     ` [linux-lvm] " Austin Gonyou
2002-10-14 16:59       ` Austin Gonyou
2002-10-14 12:14       ` Dave Jones
2002-10-14 17:11         ` Dave Jones
2002-10-14 12:19         ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submissi on Austin Gonyou
2002-10-14 17:13           ` Austin Gonyou
2002-10-14 13:03       ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submission Joe Thornber
2002-10-14 17:56         ` Joe Thornber
2002-10-14 16:09         ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submissi on Austin Gonyou
2002-10-14 21:03           ` Austin Gonyou
2002-10-15  4:00         ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submission Jens Axboe
2002-10-15  8:21           ` Jens Axboe
2002-10-15  4:57           ` Joe Thornber
2002-10-15  9:32             ` Joe Thornber
2002-10-15  4:59             ` Jens Axboe [this message]
2002-10-15  9:36               ` Jens Axboe
2002-10-15  8:13               ` Joe Thornber
2002-10-15 10:20                 ` Joe Thornber
2002-10-15  8:32                 ` Jens Axboe
2002-10-15 10:34                   ` Jens Axboe
2002-10-15 10:45                   ` Kevin Corry
2002-10-15 14:52                     ` Kevin Corry
2002-10-15 11:00                     ` Kevin Corry
2002-10-15 15:06                       ` Kevin Corry

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=20021015093608.GF5294@suse.de \
    --to=axboe@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=austin@coremetrics.com \
    --cc=joe@fib011235813.fsnet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.