On Jan 22, 2014, at 12:55 AM, Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> wrote: > > You are not CPU bound, nor hardware bandwidth bound. You are latency > bound, just like every dmcrypt user. dmcrypt adds a non trivial amount > of latency to every IO. Latency with serial IO equals low throughput. A self-encrypting drive (a drive that always & only writes ciphertext to the platters) I'd expect totally eliminates this. It's difficult finding information whether and how these drives are configurable purely for data drives (non-bootable) which ought to be easier to implement than the boot use case. For booting, it appears necessary to have computer firmware that explicitly supports the TCG OPAL spec: an EFI application might be sufficient for unlocking the drive(s) at boot time, but I'm not certain about that. It seems necessary for hibernate support that firmware and kernel support is required. Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
