From: Paul Menzel <pmenzel@molgen.mpg.de>
To: grub-devel@gnu.org, Nick Terrell <terrelln@fb.com>
Cc: Kernel Team <Kernel-team@fb.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
David Sterba <dsterba@suse.cz>,
Daniel Kiper <dkiper@net-space.pl>,
Colin Watson <cjwatson@ubuntu.com>
Subject: Re: [PATCH v3 0/2] btrfs: Add zstd support to grub btrfs
Date: Thu, 11 Oct 2018 09:56:56 +0200 [thread overview]
Message-ID: <2a45bec8-472a-0719-fd8e-b562749fb01a@molgen.mpg.de> (raw)
In-Reply-To: <C0415AB7-FD1E-4026-8AEF-02B3F7FEABC5@fb.com>
Dear Nick,
Am 10.10.2018 um 22:28 schrieb Nick Terrell:
>> On Oct 10, 2018, at 12:34 AM, Paul Menzel wrote:
>>
>> Sorry for being ignorant, but you explain, why the library needs to
>> be imported and it is not enough to use that library as an external
>> dependency?
>>
>> Importing the library means, it has to be maintained in the GRUB
>> repository, which will result in some maintenance burden.
>
> I've imported zstd because thats the way the rest of the
> decompressors are imported.
>
> We could potentially use libzstd as an external dependency, since its
> only dependency is libc and GRUB provides the definitions of the libc
> functions that zstd needs to decompress (memcpy, and memmove). Theres
> some other stuff in the library that requires libc functionality that
> GRUB doesn't provide, but that isn't used during decompression. We
> strip those files out in the import.
Thank you for the explanation.
> Let me know if you want me to switch to an external dependency.
I cannot make that decision. The main developers and the distribution
folks should comment on that.
Kind regards,
Paul
next prev parent reply other threads:[~2018-10-11 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 23:21 [PATCH v3 0/2] btrfs: Add zstd support to grub btrfs Nick Terrell
2018-10-09 23:21 ` [PATCH v3 2/2] " Nick Terrell
2018-10-11 17:55 ` Daniel Kiper
2018-10-11 18:02 ` Nick Terrell
2018-10-10 7:34 ` [PATCH v3 0/2] " Paul Menzel
2018-10-10 20:28 ` Nick Terrell
2018-10-11 7:56 ` Paul Menzel [this message]
2018-10-11 17:22 ` Daniel Kiper
[not found] ` <20181009232137.1941290-2-terrelln@fb.com>
2018-10-11 17:31 ` [PATCH v3 1/2] Import upstream zstd-1.3.6 Daniel Kiper
2018-10-11 18:15 ` [PATCH v3 0/2] btrfs: Add zstd support to grub btrfs Daniel Kiper
2018-10-11 18:56 ` Nick Terrell
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=2a45bec8-472a-0719-fd8e-b562749fb01a@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=Kernel-team@fb.com \
--cc=cjwatson@ubuntu.com \
--cc=dkiper@net-space.pl \
--cc=dsterba@suse.cz \
--cc=grub-devel@gnu.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=terrelln@fb.com \
/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).