From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Parav Pandit <parav@mellanox.com>,
Weihang Li <liweihang@huawei.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linuxarm@huawei.com" <linuxarm@huawei.com>,
Shiraz Saleem <shiraz.saleem@intel.com>
Subject: Re: Is anyone working on implementing LAG in ib core?
Date: Tue, 25 Feb 2020 09:58:51 +0200 [thread overview]
Message-ID: <20200225075851.GD5347@unreal> (raw)
In-Reply-To: <20200224182902.GS31668@ziepe.ca>
On Mon, Feb 24, 2020 at 02:29:02PM -0400, Jason Gunthorpe wrote:
> On Mon, Feb 24, 2020 at 12:52:06PM +0200, Leon Romanovsky wrote:
> > > Are you asking why bonding should be implemented as dedicated
> > > ulp/driver, and not as an extension by the vendor driver?
> >
> > No, I meant something different. You are proposing to combine IB
> > devices, while keeping netdev devices separated. I'm asking if it is
> > possible to combine netdev devices with already existing bond driver
> > and simply create new ib device with bond netdev as an underlying
> > provider.
>
> Isn't that basically what we do now in mlx5?
Yes, logically the same, the implementation of course should be
different by involving IB/core more than it is now.
>
> Logically the ib_device is attached to the bond, it uses the bond for
> IP addressing, etc.
Yes.
Thanks
next prev parent reply other threads:[~2020-02-25 7:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 3:48 Is anyone working on implementing LAG in ib core? Weihang Li
2020-02-22 23:40 ` Jason Gunthorpe
2020-02-23 0:44 ` Parav Pandit
2020-02-23 9:49 ` Leon Romanovsky
2020-02-24 7:10 ` Parav Pandit
2020-02-24 10:52 ` Leon Romanovsky
2020-02-24 18:12 ` Parav Pandit
2020-02-24 18:29 ` Jason Gunthorpe
2020-02-24 19:01 ` Parav Pandit
2020-02-24 19:23 ` Jason Gunthorpe
2020-02-24 19:41 ` Parav Pandit
2020-02-25 7:58 ` Leon Romanovsky [this message]
2020-03-02 7:22 ` liweihang
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=20200225075851.GD5347@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liweihang@huawei.com \
--cc=parav@mellanox.com \
--cc=shiraz.saleem@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).