netdev - Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48562A41.7000304@trash.net>
Date:	Mon, 16 Jun 2008 10:54:25 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>
CC:	Roland Dreier <roland.list@...il.com>, netdev@...r.kernel.org,
	rdreier@...co.com, poornima.kamath@...gic.com,
	general@...ts.openfabrics.org,
	Amar Mudrankit <amar.mudrankit@...gic.com>
Subject: Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation

Jason Gunthorpe wrote:
> On Sat, Jun 14, 2008 at 11:03:08AM -0700, Roland Dreier wrote:
>>> We have linkstate/operstate for this. How is a user supposed
>>> to configure the network device when it appears at a more or
>>> less random time from his perspective?
>  
>> Well, keep in mind that this driver is for an ethernet virtual NIC
>> that is actually
>> remote across another network (an InfiniBand fabric) -- so these devices
>> can actually appear or disappear at random times by their nature.  It's a
>> similar issue to, say, a USB ethernet adapter presents -- there's no sane way
>> to have operstate set for a device that hasn't been attached yet.
> 
> I think that is only a fair analogy if the VNIC used some kind of
> hot-plug auto discovery procedure like USB does. As soon as you
> require the administrator to run a command to bind a device to a VNIC
> GID you are much more like a tunnel device and the ethernet device
> should exist from the moment the administator creates it up until the
> administator destroys it. The state of the connection to the VNIC
> should be reflected in some way other than device presence.

Fully agreed.
--
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