On Tuesday, 12/11/2001 at 05:34 EST, "Patterson, Ross" <[EMAIL PROTECTED]> wrote: > Alan Altmark <[EMAIL PROTECTED]> writes: > > Nah. Instead of VCTC, use z/VM 4.2 and guest LANs with virtual > > HiperSockets. > > Did I miss something? The "zSeries HiperSockets" Redpaper > said that HiperSockets are QDIO devices, and that they use > the binary-only "qeth" device driver. If not, Nick's still > right in suggesting a split between kernel-release-sensitive > (i.e. source) and IBM-proprietary (i.e. binary) portions.
Sorry, I thought we were talking about an MTU/IOBUFFERSIZE issue, which HiperSockets addresses. > > I don't mean to say that the driver's design won't change (I > > don't know), > > but keep in mind that such a change isn't free, and that > > changing it is a > > business decision, not a technical one. > > Sure. And hopefully IBM's business partners, SuSE and Red Hat at > least, will remind IBM of why it would be good for business, both > theirs and IBM's. And I hope they are making that requirement known via their established IBM business channels, not via this list. Regards, Alan Senior Software Engineer z/VM, TCP/IP, VIF, and Linux for zSeries Development, Endicott, NY Phone 607.752.6027 fax 607.752.1497 t/l 852
