I was hoping for a more advanced method than just blacklisting drivers. :)
Anyways, it seems that first june there was a patch
[PATCH] btrfs: advertise which crc32c implementation is being used
at module load
that is getting merged lately, so In the near future I will be able to
see on btrfs load what driver is in use.
On 05/06/2016 22:33, Nicholas D Steeves wrote:
Hi Alberto,
On 5 June 2016 at 15:37, Alberto Bursi <alberto.bursi@xxxxxxxxxx> wrote:
Hi, I'm running Debian ARM on a Marvell Kirkwood-based 2-disk NAS.
Kirkwood SoCs have a XOR engine that can hardware-accelerate crc32c
checksumming, and from what I see in kernel mailing lists it seems to have a
linux driver and should be supported.
I wanted to ask if there is a way to test if it is working at all.
How do I force btrfs to use software checksumming for testing purposes?
Is there a mv_xor.ko module you can blacklist? I'm not familiar with
the platform, but I imagine you'll have to blacklist it and reboot,
because I'm guessing the module can't be removed once it's loaded.
'just a guess,
Nicholas
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
