netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Steve Wise <swise@opengridcomputing.com>
Cc: rdreier@cisco.com, sean.hefty@intel.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Re: [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts.
Date: Wed, 19 Sep 2007 14:56:13 +0400	[thread overview]
Message-ID: <20070919105612.GA31158@2ka.mipt.ru> (raw)
In-Reply-To: <46EE9C50.7070406@opengridcomputing.com>

Hi Steve.

On Mon, Sep 17, 2007 at 10:25:04AM -0500, Steve Wise (swise@opengridcomputing.com) wrote:
> >Does creating the whole new netdevice is a too big overhead, or is it
> >considered bad idea?
> 
> I think its too big overhead, and pretty invasive on the low level cxgb3 
> driver.  I think having a device in the 'ifconfig -a' after iw_cxgb3 is 
> loaded and devices discovered would be a good thing for the admin.  This 
> is the angle Roland suggested.  I'm just not sure how to implement it.
> 
> But if someone could explain how I might create this full netdevice as a 
> pseudo device on top of the real one, maybe I could implement it.
> 
> Note that non TCP traffic still needs to utilize this interface for ND 
> to work properly with the RDMA core.

Just a though - what about allowing secondary addresses with the same
address as main one? I.e. change bit of the core code to allow creating
aliases with the same address as main device, so that you would be able
to create ':iw' alias during rdma device initialization?

If this solution is not acceptible, then I belive your alias change is
the way to go.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2007-09-19 10:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 19:16 [PATCH v2] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts Steve Wise
2007-09-13 19:54 ` [ofa-general] " Sean Hefty
2007-09-15 14:07   ` Steve Wise
2007-09-23 20:33   ` Steve Wise
2007-09-14 13:09 ` [ofa-general] " Evgeniy Polyakov
2007-09-14 16:06   ` Roland Dreier
2007-09-15 15:56   ` Steve Wise
2007-09-16 14:22     ` [ofa-general] " Evgeniy Polyakov
2007-09-17 15:25       ` Steve Wise
2007-09-19 10:56         ` Evgeniy Polyakov [this message]
2007-09-21 15:10           ` Steve Wise
2007-09-17 16:09     ` Sean Hefty
2007-09-17 16:17       ` Evgeniy Polyakov

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=20070919105612.GA31158@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --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 \
    --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 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).