From: Jens Axboe <axboe@suse.de>
To: Dave Olien <dmo@osdl.org>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org,
kevcorry@us.ibm.com, agk@sourceware.org
Subject: Re: [RFC] [PATCH] move bio code from dm into bio
Date: Fri, 21 Jan 2005 10:02:02 +0100 [thread overview]
Message-ID: <20050121090202.GA2790@suse.de> (raw)
In-Reply-To: <20050120235826.GA3041@osdl.org>
On Thu, Jan 20 2005, Dave Olien wrote:
>
> Jens, last December you observed there was bio code
> duplicated in the dm drivers.
Yep
> Here are a collection of patches that implements
> support for local bio and bvec pools into bio.c and then
> removes the duplicate bio code from the dm drivers.
>
> It also replaces a call to alloc_bio() in dm.c with
> a call to use a local bio pool. This removes a
> deadlock case in that code.
>
> These patches are against 2.6.11-rc1. If that's not
> a good source version to patch against, let me now
> what versions I should generate patches for.
Just check if they apply to current BK tree, in general it's just best
to do patches against latest -rc1-bkX (or just the bk tree, if you use
that).
But the patch looks good, the bio_set approach is the cleanest way to
fix it I think. It will be easy to fix the bounce deadlock as well, by
adding a bio_set_bounce to mm/highmem.c as well.
Thanks for doing this! I'll review the patch in detail, the concept and
solution is definitely good though.
--
Jens Axboe
next prev parent reply other threads:[~2005-01-21 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:58 [RFC] [PATCH] move bio code from dm into bio Dave Olien
2005-01-21 9:02 ` Jens Axboe [this message]
2005-01-21 18:26 ` Dave Olien
2005-01-21 18:26 ` Dave Olien
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=20050121090202.GA2790@suse.de \
--to=axboe@suse.de \
--cc=agk@sourceware.org \
--cc=dm-devel@redhat.com \
--cc=dmo@osdl.org \
--cc=kevcorry@us.ibm.com \
--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 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.