From: Nikanth Karthikesan <knikanth@suse.de>
To: Jens Axboe <jens.axboe@oracle.com>, Alasdair G Kergon <agk@redhat.com>
Cc: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] delay initializing queue for request-based dm
Date: Sat, 8 Aug 2009 10:25:53 +0530 [thread overview]
Message-ID: <200908081025.54154.knikanth@suse.de> (raw)
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.
Thanks
Nikanth
WARNING: multiple messages have this Message-ID (diff)
From: Nikanth Karthikesan <knikanth@suse.de>
To: Jens Axboe <jens.axboe@oracle.com>, Alasdair G Kergon <agk@redhat.com>
Cc: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>,
Hannes Reinecke <hare@suse.de>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] delay initializing queue for request-based dm
Date: Sat, 8 Aug 2009 10:25:53 +0530 [thread overview]
Message-ID: <200908081025.54154.knikanth@suse.de> (raw)
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.
Thanks
Nikanth
next reply other threads:[~2009-08-08 4:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 4:55 Nikanth Karthikesan [this message]
2009-08-08 4:55 ` [PATCH 0/2] delay initializing queue for request-based dm Nikanth Karthikesan
2009-08-10 10:48 ` [PATCH-v2 " Nikanth Karthikesan
2009-08-10 10:48 ` Nikanth Karthikesan
2009-08-11 9:32 ` [PATCH-v3 " Nikanth Karthikesan
2009-08-11 9:32 ` 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=200908081025.54154.knikanth@suse.de \
--to=knikanth@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=k-ueda@ct.jp.nec.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.