From owner-svn-src-head@freebsd.org Fri May 25 15:57:39 2018 Return-Path: Delivered-To: svn-src-head@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 755C5EEB4F6; Fri, 25 May 2018 15:57:39 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (unknown [IPv6:2a01:4f8:d12:604::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0924387019; Fri, 25 May 2018 15:57:38 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w4PFvLNW027521 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 25 May 2018 17:57:21 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: src-committers@freebsd.org Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w4PFvHHe035432 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 25 May 2018 22:57:17 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: svn commit: r333388 - in head: . share/man/man4 sys/confsys/dev/nxge sys/modules sys/modules/nxge tools/kerneldoc/subsys tools/toolstools/tools/nxge usr.sbin/bsdconfig/share To: Brooks Davis References: <20180523193027.825583BC@spqr.komquats.com> <5B05C6AC.6010202@grosbein.net> <20180523202228.GC58848@spindle.one-eyed-alien.net> Cc: Cy Schubert , Stefan Esser , "rgrimes@freebsd.org" , Mark Linimon , Gleb Smirnoff , Sean Bruno , "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" From: Eugene Grosbein Message-ID: <5B083259.1000009@grosbein.net> Date: Fri, 25 May 2018 22:57:13 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20180523202228.GC58848@spindle.one-eyed-alien.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Mailman-Approved-At: Fri, 25 May 2018 16:32:55 +0000 X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2018 15:57:39 -0000 24.05.2018 3:22, Brooks Davis wrote: >>> Except for old computers and old software that segfaults on 64-bit, how many people still use i386? >>> Full disclosure: I'd like to see i386 deorbited before I retire. >> Plese don't. I routinely use FreeBSD11/i386 for cheap VPS hosts having less than 2G memory >> because amd64 has noticeable overhead. I even have ZFS-only i386 VPS, here is live example with 1G only: >> >> Mem: 10M Active, 69M Inact, 230M Wired, 685M Free >> ARC: 75M Total, 1953K MFU, 31M MRU, 172K Anon, 592K Header, 42M Other >> 3500K Compressed, 29M Uncompressed, 8.61:1 Ratio >> Swap: 1024M Total, 1024M Free >> >> The VPS has only 20G of disk space and ZFS compression gives >> compressratio 2.22x for ports, 2.51x for src, 2.29x for obj >> and 1.95x for installed i386 system plus other software and data. > > I think we're quite a ways from being ready to axe i386. > > For VPS applications, we should probably get x32 support in place which > should give us the best of both worlds. > > That said, we either need to rev the i386 ABI to use a 64-bit time_t or > kill it in the not to distant future or we risk embedded systems failing > in place in 2038. If we assume a 15 year life for most equipment to > fail electrically or mechanically that says FreeBSD 13 shouldn't support > the current i386 ABI. Why everyone's talking of hardware only? FreeBSD/i386 as virtual machine guest with memory-intensive kernel subsystems like ZFS and/or networking tasks using plenty of mbufs benefits significantly comparing with amd64 version. It runs just fine, why even consider killing it?