From owner-freebsd-arch@freebsd.org Thu May 17 18:09:32 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9DF5EDBC9B for ; Thu, 17 May 2018 18:09:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C1D16DC26; Thu, 17 May 2018 18:09:32 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x242.google.com with SMTP id a20-v6so2478844pfo.0; Thu, 17 May 2018 11:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=e5nPAWi1kPA0TaF0B66le1WzSofzQXdd8WDWx/9W/H0=; b=MmMfLBIYhlkx4EIxdsmUvVMyeK2dHTe8KE1+FCdSOhOYQI2mq0IsTkdZuXdU3vVNMV tam0NRq8QcsuwTr9H1t97zEuV3eiSJnjQzLrRTztx2GsO8o0ome39pNcPVd11NVlA2JG 8f3AYKtRWpx1lNSOitvrmm/iP6Be5qjMeKCMtcv2fZhNkli2mYohfG/ODuJzJFktsAco WLI4Vq71m7mVCLvWLjzEGn+EWpbiKpCWhLRK8rz261m0t7NBRYkJ801Q54YOUu44GJyh Qm0IhmZJJipJI5CmdXFoDbd+LUPJdmnwX8+0pZvNma1Uve5k7BtWygdsuIWmQ+ExKcJz yUqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=e5nPAWi1kPA0TaF0B66le1WzSofzQXdd8WDWx/9W/H0=; b=Jrhzaq9x+KqIizyuSIIBAdBa+2WtuqM7Pvs/Ve5L96zMejxLDSImSuUbfpA3TmiEGD w4dU+N3val0DB9SrkmMYXF06xfJzL/dQvSU7wsDceSV3aiG8RylG3pgfASZD+c3oJbeg ySGYCs5Sriirc5cG+5RSLhvEwN6qkxnfxhBgoQ/c/SEsTSei00S3gZNq07bF34M7Sinz sQlC7yRoe3Db+BqjP7Kb8PExLOO+pDSL7+PIHTHkkd2oK2PSWH+5WEh+A1zywJRyEg4e 7ZDfDpZiemp9bvGJ69hf8sXaNjJl4tuIyrHff7kE53XcubOo3QsHfUE6fPQeNR9ZoBMA L4Lw== X-Gm-Message-State: ALKqPwedetVPl2nEBdkrufkmJs8on9Xy1ynAXpk8qsmKbnlOMPPdsd6A jSl99a74lUJi3A/Jto1ljMEPB7dJ X-Google-Smtp-Source: AB8JxZrDVmKHmZJp9abJtU6VAVCO43MBQpHeWizN+Blmm+BmzsMB8b6j31KnEWpuQUVboaH5OykzuQ== X-Received: by 2002:a63:5f10:: with SMTP id t16-v6mr81789pgb.52.1526580570987; Thu, 17 May 2018 11:09:30 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-130.dsl.bell.ca. [70.49.169.130]) by smtp.gmail.com with ESMTPSA id o84-v6sm12377941pfi.27.2018.05.17.11.09.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 11:09:30 -0700 (PDT) Sender: Mark Johnston Date: Thu, 17 May 2018 14:09:27 -0400 From: Mark Johnston To: Conrad Meyer Cc: "freebsd-arch@freebsd.org" Subject: Re: enabling kernel dump options in GENERIC Message-ID: <20180517180927.GB5515@raichu> References: <20180517172412.GA92051@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 18:09:33 -0000 On Thu, May 17, 2018 at 10:57:35AM -0700, Conrad Meyer wrote: > On Thu, May 17, 2018 at 10:24 AM, Mark Johnston 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).