search for: cryptographic_accelerator

...U support. > What would we have to do to get that hardware performance improvement? Just upgrade Samba to some version patched with Metze stuffs or is there also some drivers to be compiled and loaded into Kernel? The hardware seems to be included directly in CPU: https://en.wikipedia.org/wiki/Cryptographic_accelerator gave me: https://en.wikipedia.org/wiki/AES_instruction_set Then looking for my own desktop CPU I found that page from Intel where there is a line for "Intel® AES New Instructions" near the bottom: http://ark.intel.com/products/63697/Intel-Core-i7-3930K-Processor-12M-Cache-up-to-3_80-GHz...

...rade Samba to some version patched with Metze stuffs or is there > also some drivers to be compiled and loaded into Kernel? I believe Metze's patches require OpenSSL, but he needs to comment on that. > The hardware seems to be included directly in CPU: > https://en.wikipedia.org/wiki/Cryptographic_accelerator > gave me: > https://en.wikipedia.org/wiki/AES_instruction_set Yep. Samba does not use that directly but utilizes some crypto library. Given that there's dozens of "standard" crypto libraries out there with varying algorithm/hardware/nameit support, it's a bit difficult to...

I disabled client signing from the client side, via OS X's global nsmb.conf file: https://discussions.apple.com/message/30282470#30282470 The performance was back to over 600 MB/s, as compared to 60 MB/s with signing. It just seems a bit weird to me that Apple, in response to the Badlock bug, would have changed the OS X client default to something with such drastic performance implications,