Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 May 2018 14:09:27 -0400
From:      Mark Johnston <markj@freebsd.org>
To:        Conrad Meyer <cem@freebsd.org>
Cc:        "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Subject:   Re: enabling kernel dump options in GENERIC
Message-ID:  <20180517180927.GB5515@raichu>
In-Reply-To: <CAG6CVpX9gUL14rqOwycrkknuBgUe5DCa9tyb=jJB_EYq1iPsGw@mail.gmail.com>
References:  <20180517172412.GA92051@raichu> <CAG6CVpX9gUL14rqOwycrkknuBgUe5DCa9tyb=jJB_EYq1iPsGw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 17, 2018 at 10:57:35AM -0700, Conrad Meyer wrote:
> On Thu, May 17, 2018 at 10:24 AM, Mark Johnston <markj@freebsd.org> wrote:
> > Hi,
> >
> > Over the past couple of years, a number of kernel dump features have
> > been added: encryption, compression and dumping to a remote host
> > (netdump). These features are currently all omitted from GENERIC.
> 
> I don't have anything substantive to add, but as someone who has
> code-reviewed, written, and/or used a bunch of these features at
> $DAYJOB, I'd love to see them built by default in GENERIC — even if
> disabled by default (compression — the others don't have a sane
> default configuration).  I don't think GZIO is especially useful if we
> enable ZSTDIO, but at the same time I think it's harmless to enable as
> an option.

Yeah, given that the size increase is very small, I didn't see a reason
to specifically exclude GZIO. I can also imagine a scenario where one
uses GZIO+netdump to send dumps to a host lacking zstd(1).



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180517180927.GB5515>