Date: Mon, 9 May 2016 16:25:28 +1000 From: Peter Jeremy <peter@rulingia.com> To: Lev Serebryakov <lev@FreeBSD.org> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, George Neville-Neil <gnn@neville-neil.com>, fs@freebsd.org Subject: Re: Fwd: The Morning Paper: NOVA - A log-structured file system for hybrid volatile/non-volatile main memories Message-ID: <20160509062528.GB57227@server.rulingia.com> In-Reply-To: <1058947919.20160508140842@serebryakov.spb.ru> References: <4188b6afbe9e5d43111fef4d4ae5e599a57.20160506051425@mail23.atl91.mcsv.net> <2BE88161-D83A-4265-9EC3-C2F7F7033E93@neville-neil.com> <59877.1462639101@critter.freebsd.dk> <07228891.20160508134321@serebryakov.spb.ru> <62925.1462704459@critter.freebsd.dk> <1058947919.20160508140842@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2016-May-08 14:08:47 +0300, Lev Serebryakov <lev@FreeBSD.org> wrote: >Hello Poul-Henning, > >Sunday, May 8, 2016, 1:47:39 PM, you wrote: > >> The problem with that kind of hardware is that either you specialize >> 100% for that vendors product, with resulting lock-in, or you satisfy >> yourself with a generic solution which works an anything sensible. > >> I don't think FreeBSD has the bandwidth for anything but the second opti= on. > > Really, Intel is not "that vendor" now. It is THE Vendor. FreeBSD has a = LOT >of specialization for this vendor (all i386 code, NVMe, and other), and ma= ny >thing from Intel (or which becomes widespread in Intel-based systems, like >PCI, which is not exactly "from Intel", of course) becomes industrial >standard. There's a difference between FreeBSD having i386/amd64 as the main Tier-1 platform and supporting hardware that is only supported by some (not even all) x86 CPUs manufactured by Intel. There are a number of other vendors that supply i386/amd64-compatible CPUs. Whilst we do have CPU-specific code (for CPU initialisation and hwpmc), there's a big step between that and supporting a filesystem that requires vendor-specific hardware and a vendor-specific CPU. > I don't think such type of memory will be very-Intel-specific for long. HP >works on something comparable, and other companies too. "Something comparable" doesn't mean it'll be compatible - Intel have a vested interest in locking customers into their CPUs. And the hype surrounding "The Machine" has been toned down significantly - suggesting that HP are having a harder time productizing their NVM than they expected. --=20 Peter Jeremy --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXMC1YXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0XAIQAIRWSAas0E6a6Kzt9irEgSPP hFoiQMzdvBSUgPMwMs6gwURd5ezWLnvFojgHx8AZ+Be9ycs/bqV4PY52VWj0LBLp xkbx67DZfxjNTp3WfhFzGsnikQ9aRfb3e3aKyo8ISjMP/QmB1kLnk+cmEAXXIJUg xeESXtZcX+Rw799vqXpKVG1h0de47+8urQXQ5HEq4JkPz31nB00oFOAjssWY1U9o zbp54igEHzb8kkF8T0bLfBiBZQ4+s/qi4+staT3oSnNzFTbu7cqfaCTK78ecZlQt vhL9GCZOMG3MnBa/p67I1vEDFN/cZdQJL9yyQJ6mNgdR0FF/884hmc+L4EVzw4Gi dcK1m3uBUNDGHzhxqS90mS+ZgmQGtmJ7aYDBJMCyrQ3mhsFEfP9iFlHIusVCrv6P WsmaHQCNWlGr3aEhwqkH1f+Qmxf9w+9inbQMsSj2QY7+bGck7GoryZM72hX9agVu WjtZd4QWJRp+n+Zj2M5YKPR5hqN2QyUhjn+neTsx96ZJlSa+Mfn4RRCebhK/jfBh cee2b4S79fA5ObDYeaxMpBIwYnJLWgiiuUwrXwTDgmy/vDOwUXO9OjIkMnUpxd87 yiUSGFgSEetSAFnHtWwj7O1/eXG+Uv/+5hLYNhXdVl0RzR1sxrZKLtNIZwuMCSIS d19myfHoqVN788Mx7AcM =XVCz -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160509062528.GB57227>