netdev
[Top] [All Lists]

Re: [PATCH] ipv6: alternative version of S/390 shared NIC support

To: hadi@xxxxxxxxxx
Subject: Re: [PATCH] ipv6: alternative version of S/390 shared NIC support
From: Christian Bornträger <christian@xxxxxxxxxxxxxxx>
Date: Tue, 18 Jan 2005 00:37:57 +0100
Cc: Christoph Hellwig <hch@xxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, pavlic@xxxxxxxxxx, waldi@xxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <1106003481.1035.35.camel@xxxxxxxxxxxxxxxx>
References: <20050116115431.GA13617@xxxxxx> <20050117225946.GA11845@xxxxxx> <1106003481.1035.35.camel@xxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: KMail/1.7.1
jamal wrote:
> On Mon, 2005-01-17 at 17:59, Christoph Hellwig wrote:
> > The problem is again that the OS instances don't talk to each
> > (well they can, but not in the driver), so your demux code would
> > have to move into the device firmware, and that'd probably change
> > the device <-> OS interface completely.
>
> qeth_qdio_input_handler() seems to know what "card" the packet came on,
> no? Could you not use this information to select the proper netdevice?
> Actually, how does that work? Each OS instance would get the same driver
> invoked but you will never see any othe instances "cards"?

I am trying a small simplification here:
Each physical network adapter offers hundreds of device addresses. You need 
3 of them to have one logical network adapter(read,write,data). S/390 has 
hardware supported virtualization. Therefore can then use the hypervisor 
(LPAR or z/VM) to give specific LPARs or VM guests exactly 3 device 
addresses out of these hundreds. 
The qeth driver has to register the IP address at the logical network card 
(using 3 device addresses) Afterwards the physical network card knows which 
packet belongs to which device numbers.

cheers Christian

<Prev in Thread] Current Thread [Next in Thread>