Pleas, close this issue. This feature is not needed without main T10 code, I don`t see any progress on T10, and I will not spend time to update this patch.
Alexander Boyko
added a comment - Pleas, close this issue. This feature is not needed without main T10 code, I don`t see any progress on T10, and I will not spend time to update this patch.
It seem the feature freeze for 2.5 is the end of July. It would be good to refresh this patch if the T10 code is targeted for the 2.5 release.
Keith Mannthey (Inactive)
added a comment - It seem the feature freeze for 2.5 is the end of July. It would be good to refresh this patch if the T10 code is targeted for the 2.5 release.
Keith, it will take time. The current kernel version is 3.9, but Lustre base on 2.6.32-279. May be I need to create and push t10 code to kernel in parallel. The T10 for Lustre has specific restrictions - only 512 and 4096 sector size and aligned data, using this the code is more productive than the general implementation.
Alexander Boyko
added a comment - Keith, it will take time. The current kernel version is 3.9, but Lustre base on 2.6.32-279. May be I need to create and push t10 code to kernel in parallel. The T10 for Lustre has specific restrictions - only 512 and 4096 sector size and aligned data, using this the code is more productive than the general implementation.
It is possible to accelerate the Kernels T10 rather than re-implement the T10 framework in Lustre?
Do we know why the T10 is not ASM accelerated in the kernel or the status of mainline in this regard?
Keith Mannthey (Inactive)
added a comment - It is possible to accelerate the Kernels T10 rather than re-implement the T10 framework in Lustre?
Do we know why the T10 is not ASM accelerated in the kernel or the status of mainline in this regard?
While this particular patch provides hardware support for the T10-DIF CRC algorithm for general use in the libcfs library, and is not concerned with any actual T10-DIF/DIX usage, I understand the reluctance to use apparently unnecessary code.
This is the first patch in a series designed to provide end-to-end T10-DIX support for Lustre clients; I will open another, high-level ticket describing it.
Nathan Rutman
added a comment - While this particular patch provides hardware support for the T10-DIF CRC algorithm for general use in the libcfs library, and is not concerned with any actual T10-DIF/DIX usage, I understand the reluctance to use apparently unnecessary code.
This is the first patch in a series designed to provide end-to-end T10-DIX support for Lustre clients; I will open another, high-level ticket describing it.
Keith, if you are talking about crc T10, the kernel implementation is very slow and take much cpu resources.
Andreas, you are right size of BRW RPC will be increased by sizeof(crc) * number of sectors for the bulk.
Alexander Boyko
added a comment - Keith, if you are talking about crc T10, the kernel implementation is very slow and take much cpu resources.
Andreas, you are right size of BRW RPC will be increased by sizeof(crc) * number of sectors for the bulk.
A good amount of kernels have T10 support at this point. Is the kernels T10 implementation not usable for your needs?
Keith Mannthey (Inactive)
added a comment - A good amount of kernels have T10 support at this point. Is the kernels T10 implementation not usable for your needs?
Close bug per request.