From: Roland Dreier <rdreier@cisco.com>
To: Steve Wise <swise@opengridcomputing.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: Wed, 05 Sep 2007 08:18:00 -0700 [thread overview]
Message-ID: <ada642puonr.fsf@cisco.com> (raw)
In-Reply-To: <46DD762F.80904@opengridcomputing.com> (Steve Wise's message of "Tue, 04 Sep 2007 10:13:51 -0500")
> > 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.
next prev parent reply other threads:[~2007-09-05 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 21:39 [PATCH RFC] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts with the host stack Steve Wise
2007-08-23 21:39 ` [ofa-general] " Steve Wise
2007-08-31 4:27 ` Roland Dreier
2007-08-31 4:27 ` [ofa-general] " Roland Dreier
2007-09-04 15:13 ` Steve Wise
2007-09-05 15:18 ` Roland Dreier [this message]
2007-09-05 15:40 ` Steve Wise
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=ada642puonr.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ewg@lists.openfabrics.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sean.hefty@intel.com \
--cc=swise@opengridcomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.