From: Daniel Kiper <dkiper@net-space.pl>
To: Nick Terrell <terrelln@fb.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
"grub-devel@gnu.org" <grub-devel@gnu.org>,
Daniel Kiper <dkiper@net-space.pl>,
Kernel Team <Kernel-team@fb.com>, David Sterba <dsterba@suse.cz>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] btrfs: Add zstd support to grub btrfs
Date: Thu, 11 Oct 2018 19:22:19 +0200 [thread overview]
Message-ID: <20181011172219.GD30679@router-fw-old.i.net-space.pl> (raw)
In-Reply-To: <C0415AB7-FD1E-4026-8AEF-02B3F7FEABC5@fb.com>
On Wed, Oct 10, 2018 at 08:28:27PM +0000, Nick Terrell wrote:
> > On Oct 10, 2018, at 12:34 AM, Paul Menzel <pmenzel@molgen.mpg.de> 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.
>
> Let me know if you want me to switch to an external dependency.
I do not think it is possible. Or it can be at least difficult. Even if
it is possible it would require a major rework of GRUB build machine.
So, even if current solution is not perfect I would like to stick to it.
And zstd library integration is not very difficult. So, I do not think
it will add a lot of burden in the future.
Daniel
next prev parent reply other threads:[~2018-10-11 17:22 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
2018-10-11 17:22 ` Daniel Kiper [this message]
[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=20181011172219.GD30679@router-fw-old.i.net-space.pl \
--to=dkiper@net-space.pl \
--cc=Kernel-team@fb.com \
--cc=dsterba@suse.cz \
--cc=grub-devel@gnu.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--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).