. (I received couple of private emails on this, so looks like I confused you and I'm writing again to clear the air on this).
- Uses btrfs compression framework, so compression and then encryption is not possible. However yet evaluate if there are encryption algorithm which can compress as well.
It should be compression and then encryption. I didn't mean to say the other way around. However the btrfs encoding framework is designed to handle any one of it in an elegant manner. So as of user can configure either encryption OR compression by design. Further for users who are looking for both compression and encryption. There are two ways that we could implement in future in the btrfs. One enhance the btrfs encoding framework so that it can accommodate two cascaded engines like compression and followed by encryption. Or (mostly) a better approach would be to evaluate a single encoding engine (algorithm) which can do both (compression and then encryption). Which I think will be less invasive within btrfs, and probably be more efficient. Hope I sound clearer now. Sorry if I wasn't before. . I have put up a doc here: https://docs.google.com/document/d/1fq9snDM_4ikn44UDNErjHqKXgZHukiJWS4Il3qVhm3M/edit?usp=sharing For your kind review and suggestions. Thanks, Anand -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
