linux-kernel - [PATCH-v2 0/2] delay initializing queue for request-based dm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200908101618.12508.knikanth@suse.de>
Date:	Mon, 10 Aug 2009 16:18:12 +0530
From:	Nikanth Karthikesan <knikanth@...e.de>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Alasdair G Kergon <agk@...hat.com>,
	Kiyoshi Ueda <k-ueda@...jp.nec.com>,
	Hannes Reinecke <hare@...e.de>, dm-devel@...hat.com,
	linux-kernel@...r.kernel.org, Mike Snitzer <snitzer@...hat.com>
Subject: [PATCH-v2 0/2] delay initializing queue for request-based dm

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/