From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation Date: Sat, 14 Jun 2008 13:03:58 -0600 Message-ID: <20080614190358.GU22807@obsidianresearch.com> References: <20080610205633.11186.45499.stgit@dale> <20080610210918.11186.64253.stgit@dale> <484F751F.7030407@trash.net> <48513E4E.4040601@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Amar Mudrankit , netdev@vger.kernel.org, rdreier@cisco.com, general@lists.openfabrics.org, Patrick McHardy , poornima.kamath@qlogic.com To: Roland Dreier Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: general-bounces@lists.openfabrics.org Errors-To: general-bounces@lists.openfabrics.org List-Id: netdev.vger.kernel.org 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. Jason