Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756431AbXIEPS0 (ORCPT ); Wed, 5 Sep 2007 11:18:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756800AbXIEPSI (ORCPT ); Wed, 5 Sep 2007 11:18:08 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]:30827 "EHLO sj-iport-4.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756692AbXIEPSF (ORCPT ); Wed, 5 Sep 2007 11:18:05 -0400 X-IronPort-AV: E=Sophos;i="4.20,210,1186383600"; d="scan'208";a="9502974" To: Steve Wise Cc: general@lists.openfabrics.org, ewg@lists.openfabrics.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, sean.hefty@intel.com Subject: Re: [PATCH RFC] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts with the host stack. X-Message-Flag: Warning: May contain useful information References: <1187905185.5547.13.camel@stevo-desktop> <46DD762F.80904@opengridcomputing.com> From: Roland Dreier Date: Wed, 05 Sep 2007 08:18:00 -0700 In-Reply-To: <46DD762F.80904@opengridcomputing.com> (Steve Wise's message of "Tue, 04 Sep 2007 10:13:51 -0500") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.20 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 05 Sep 2007 15:18:00.0590 (UTC) FILETIME=[F24F4AE0:01C7EFCF] Authentication-Results: sj-dkim-2; header.From=rdreier@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1153 Lines: 27 > > What's wrong with my suggestion of having the iwarp driver create an > > "iwX" interface to go with the normal "ethX" interface? It seems > > simpler to me, and there's a somewhat similar precedent with how > > mac80211 devices create both wlan0 and wmaster0 interfaces. > > - R. > > It seemed much more painful for me to implement. :-) > > I'll look into this, but I think for this to be done, the changes must > be in the cxgb3 driver, not the rdma driver, because the guts of the > netdev struct are all private to cxgb3. Remember that this interface > needs to still do non TCP traffic (like ARP and UDP)... > > Maybe you have something in mind here that I'm not thinking about? No, I was just spouting off. But the whole "create a magic alias" seems kind of unfriendly to the user. Maybe as you said, the cxgb3 net driver could create the alias for the iw_cxgb3 driver? - R. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/