From mboxrd@z Thu Jan 1 00:00:00 1970 From: lm@mcvoy.com (Larry McVoy) Date: Mon, 20 Nov 2017 11:39:39 -0800 Subject: [TUHS] UNIX on S/370 In-Reply-To: <20171120193651.GH9146@mcvoy.com> References: <20171120160504.3C46B18C091@mercury.lcs.mit.edu> <20171120191055.GF9146@mcvoy.com> <20171120193651.GH9146@mcvoy.com> Message-ID: <20171120193939.GI9146@mcvoy.com> On Mon, Nov 20, 2017 at 11:36:51AM -0800, Larry McVoy wrote: > On Mon, Nov 20, 2017 at 12:36:05PM -0700, Warner Losh wrote: > > On Mon, Nov 20, 2017 at 12:10 PM, Larry McVoy wrote: > > > > > On Mon, Nov 20, 2017 at 02:07:27PM -0500, Paul Winalski wrote: > > > > It would mean that you wouldn't have to implement machine check > > > > support and other hardware error handling. The VM hypervisor would do > > > > that for you. It would also let you run multiple versions of UNIX > > > > simultaneously. Very convenient if you're doing kernel or driver > > > > development. > > > > > > Indeed. I'm currently trying to convince Netflix that the way to get the > > > most performance out of a NUMA machine is to boot a different kernel on > > > each NUMA domain. One way we might demo that is on a 4 domain system > > > lock down 3 hypervisors and their guest OS to 3/4 of the NUMA domains > > > and give the host kernel the 4th. > > > > Having a single nic presents a bit of a challenge for this... I look > > forward to this demo... > > Nope, do disks/mics/mem per domain. So no bonding. Sorry s/mics/nics/ -- --- Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm