[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] commit 6d2a78e783416ba99e36beb1d4395b785b34e867 avoids dm integrity support
- From: "Martin K. Petersen" <martin petersen oracle com>
- To: device-mapper development <dm-devel redhat com>
- Cc: Alasdair G Kergon <agk redhat com>, "Martin K. Petersen" <martin petersen oracle com>, Jens Axboe <jens axboe oracle com>
- Subject: Re: [dm-devel] commit 6d2a78e783416ba99e36beb1d4395b785b34e867 avoids dm integrity support
- Date: Mon, 30 Mar 2009 14:39:04 -0400
>>>>> "Kiyoshi" == Kiyoshi Ueda <k-ueda ct jp nec com> writes:
Kiyoshi> I found this commit (6d2a78e783416ba99e36beb1d4395b785b34e867)
Kiyoshi> in the recent Linus's git makes every block device share single
Kiyoshi> mempool for integrity cloning.
Yeah, until this patch went in I had the integrity stuff hanging off of
the bio_set to avoid the deadlocks you mention. When this issue came up
a few weeks ago Jens suggested the changes in the commit above:
http://marc.info/?l=linux-kernel&m=123662652229483
I just talked to him and we're going to back this patch for now. Short
term I guess we'll have to settle for a separate pool in the bio_set for
integrity vectors.
--
Martin K. Petersen Oracle Linux Engineering
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]