From: Nikanth Karthikesan <knikanth@suse.de>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
Hannes Reinecke <hare@suse.de>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Mike Snitzer <snitzer@redhat.com>
Subject: [PATCH-v2 0/2] delay initializing queue for request-based dm
Date: Mon, 10 Aug 2009 16:18:12 +0530 [thread overview]
Message-ID: <200908101618.12508.knikanth@suse.de> (raw)
In-Reply-To: <200908081025.54154.knikanth@suse.de>
On Saturday 08 August 2009 10:25:53 Nikanth Karthikesan wrote:
> Hi
>
> Currently for device-mapper devices, we initialize the mempool for requests
> and elevator at device creation time. But only request-based devices use
> the elevator and mempool. These patches change it to allocate the mempool
> and initialize the elevator only for request-based devices. This is done by
> allocating a queue at device creation time, but delaying the initialization
> of elevator and allocation of mempool till the first table load time, when
> the type of device would be known.
>
> [PATCH 1/2] Allow delaying initialization of queue after allocation
>
> [PATCH 2/2] Initialize mempool and elevator only for request-based dm
> devices
>
> Another approach would be to free the mempool and detach elevator, if it
> would be a bio-based device. But it is better to avoid initialization
> itself.
>
Changes since v1:
1. Refreshed on top of a4e7d46407d73f35d217013b363b79a8f8eafcaa
2. Added comments suggested by Mike Snitzer.
3. Cleaned up the second patch as suggested by Mike Snitzer.
Thanks
Nikanth
next prev parent reply other threads:[~2009-08-10 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 4:55 [PATCH 0/2] delay initializing queue for request-based dm Nikanth Karthikesan
2009-08-10 10:48 ` Nikanth Karthikesan [this message]
2009-08-11 9:32 ` [PATCH-v3 " Nikanth Karthikesan
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=200908101618.12508.knikanth@suse.de \
--to=knikanth@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=jens.axboe@oracle.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.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