From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Roland Dreier" Subject: Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation Date: Sat, 14 Jun 2008 11:03:08 -0700 Message-ID: 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=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, rdreier@cisco.com, poornima.kamath@qlogic.com, general@lists.openfabrics.org, Amar Mudrankit To: "Patrick McHardy" Return-path: In-Reply-To: <48513E4E.4040601@trash.net> Content-Disposition: inline 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 > 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. - R.