From: Nikolay Borisov <nborisov@suse.com>
To: Jean Fobe <jeanfobe@ime.usp.br>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs development - question about crypto api integration
Date: Thu, 29 Nov 2018 19:37:21 +0200 [thread overview]
Message-ID: <8db22a5b-14de-3e8a-241f-d7e963ea5a57@suse.com> (raw)
In-Reply-To: <CAMHc_wN+-qHc1+q6fuRCzzJ9fsE2-vwa5N3031ANpZ8+tXb7WQ@mail.gmail.com>
On 29.11.18 г. 18:43 ч., Jean Fobe wrote:
> Hi all,
> I've been studying LZ4 and other compression algorithms on the
> kernel, and seen other projects such as zram and ubifs using the
> crypto api. Is there a technical reason for not using the crypto api
> for compression (and possibly for encryption) in btrfs?
> I did not find any design/technical implementation choices in
> btrfs development in the developer's FAQ on the wiki. If I completely
> missed it, could someone point me in the right direction?
> Lastly, if there is no technical reason for this, would it be
> something interesting to have implemented?
I personally think it would be better if btrfs' exploited the generic
framework. And in fact when you look at zstd, btrfs does use the
generic, low-level ZSTD routines but not the crypto library wrappers. If
I were I'd try and convert zstd (since it's the most recently added
algorithm) to using the crypto layer to see if there are any lurking
problems.
>
> Best regards
>
next prev parent reply other threads:[~2018-11-29 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 16:43 btrfs development - question about crypto api integration Jean Fobe
2018-11-29 17:37 ` Nikolay Borisov [this message]
2018-11-30 15:22 ` Chris Mason
2018-11-30 16:27 ` Nikolay Borisov
2018-12-04 13:29 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8db22a5b-14de-3e8a-241f-d7e963ea5a57@suse.com \
--to=nborisov@suse.com \
--cc=jeanfobe@ime.usp.br \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).