[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EC6A778.1000503@hp.com>
Date: Fri, 18 Nov 2011 10:44:08 -0800
From: Rick Jones <rick.jones2@...com>
To: Ben Hutchings <bhutchings@...arflare.com>
CC: Olaf Hering <olaf@...fle.de>, netdev@...r.kernel.org,
xen-devel@...ts.xensource.com,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: [PATCH] xen-netfront: report link speed to ethtool
On 11/18/2011 09:46 AM, Ben Hutchings wrote:
> On Fri, 2011-11-18 at 17:48 +0100, Olaf Hering wrote:
>> Add .get_settings function, return fake data so that ethtool can get
>> enough information. For some application like VCS, this is useful,
>> otherwise some of application logic will get panic.
>> The reported data refers to VMWare vmxnet.
>>
>> Signed-off-by: Xin Wei Hu<xwhu@...e.com>
>> Signed-off-by: Chunyan Liu<cyliu@...e.com>
>> Signed-off-by: Olaf Hering<olaf@...fle.de>
>
> NAK, we should not just make things up.
Which raises an interesting question for a virtual interface that isn't
pretending to be a specific NIC type. What should the reported speed be?
Is it a 10/100 NIC? A 1 or 10 GbE NIC? 3.14 GbE? For other emulated
interfaces, it rather falls-out from the emulation. We can say that the
driver may not make stuff up, but it would seem what is running in the
host/hypervisor/dom0/whatever will have to. It could I suppose, decide
based on the physical NIC to which it is attached, so long as folks
using the virtual NIC don't expect its attributes to be the same from
system to system.
rick
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists