From: Steve Wise <swise@opengridcomputing.com>
To: Roland Dreier <rdreier@cisco.com>
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.
Date: Tue, 04 Sep 2007 10:13:51 -0500 [thread overview]
Message-ID: <46DD762F.80904@opengridcomputing.com> (raw)
In-Reply-To: <adaveawwcpz.fsf@cisco.com>
Roland Dreier wrote:
> > The sysadmin creates "for iwarp use only" alias interfaces of the form
> > "devname:iw*" where devname is the native interface name (eg eth0) for the
> > iwarp netdev device. The alias label can be anything starting with "iw".
> > The "iw" immediately after the ':' is the key used by the iwarp driver.
>
> 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?
Steve.
next prev parent reply other threads:[~2007-09-04 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 21:39 [ofa-general] [PATCH RFC] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts with the host stack Steve Wise
2007-08-31 4:27 ` [ofa-general] " Roland Dreier
2007-09-04 15:13 ` Steve Wise [this message]
2007-09-05 15:18 ` Roland Dreier
2007-09-05 15:40 ` [ofa-general] " Steve Wise
2007-09-05 17:27 ` Steve Wise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46DD762F.80904@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=ewg@lists.openfabrics.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=sean.hefty@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).