[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 2/2] dm: Add support for data integrity to DM
- From: "Martin K. Petersen" <martin petersen oracle com>
- To: device-mapper development <dm-devel redhat com>
- Cc: k-ueda ct jp nec com, agk sourceware org, linux-kernel vger kernel org, martin petersen oracle com, jens axboe oracle com
- Subject: Re: [dm-devel] [PATCH 2/2] dm: Add support for data integrity to DM
- Date: Mon, 29 Sep 2008 11:05:02 -0400
>>>>> "Kiyoshi" == Kiyoshi Ueda <k-ueda ct jp nec com> writes:
Kiyoshi> Creating another function (e.g. dm_table_set_integrity(t,
Kiyoshi> md)) may be better, since then you wouldn't need dm_queue()
Kiyoshi> nor need to change the function interface of
Kiyoshi> dm_table_set_restrictions() I think.
You are right. Originally I had more reasons for having that calling
interface change but that's no longer the case. I'll fan the
integrity bits out to a separate function.
--
Martin K. Petersen Oracle Linux Engineering
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]