From: Steve Wise <swise@opengridcomputing.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: general@lists.openfabrics.org, linux-kernel@vger.kernel.org
Subject: Re: [ofa-general] Updated InfiniBand/RDMA merge plans for 2.6.24
Date: Tue, 09 Oct 2007 09:15:32 -0500 [thread overview]
Message-ID: <470B8D04.30401@opengridcomputing.com> (raw)
In-Reply-To: <adair5hjh64.fsf@cisco.com>
Roland Dreier wrote:
> > No mention about the iwarp port space issue?
>
> I don't think we're at a stage where I'm prepared to merge something--
> we all agree the latest patch has serious drawbacks, and it commits us
> to a suboptimal interface that is userspace-visible.
>
Fair enough.
> > I'm at a loss as to how to proceed.
>
> Could we try to do some cleanups to the net core to make the alias
> stuff less painful? eg is there any sane way to make it possible for
> a device that creates 'eth0' to also create an 'iw0' alias without an
> assigning an address?
>
Well, "alias" interfaces really don't exist. ethX:iw is really just
adding a address record (struct in_ifaddr) to ethX. So in the current
core design, adding an alias without an address is really adding the
alias with address 0.0.0.0. And I think the core net code assumes if an
in_ifaddr struct exists for a device, then its IP address is indeed valid.
So I think the changes wouldn't be small to enhance the design to add a
concept of an alias interface.
I'll look into this more though.
Steve.
next prev parent reply other threads:[~2007-10-09 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 23:18 Roland Dreier
2007-10-07 2:02 ` [ofa-general] " Pradeep Satyanarayana
2007-10-09 15:16 ` Roland Dreier
2007-10-09 17:18 ` Sean Hefty
2007-10-09 18:49 ` Pradeep Satyanarayana
2007-10-07 16:19 ` Steve Wise
2007-10-08 23:54 ` Roland Dreier
2007-10-09 14:15 ` Steve Wise [this message]
2007-10-08 6:38 ` Jack Morgenstein
2007-10-08 14:48 ` Roland Dreier
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=470B8D04.30401@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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
Powered by JetHome