From: Stephen Hemminger <stephen@networkplumber.org>
To: Kamil Vojanec <vojanec@cesnet.cz>
Cc: "lihuisong (C)" <lihuisong@huawei.com>,
dev@dpdk.org, Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: [PATCH v2 1/2] net/bonding: introduce direct link bonding mode
Date: Tue, 3 Dec 2024 10:18:46 -0800 [thread overview]
Message-ID: <20241203101846.4eb39fb9@hermes.local> (raw)
In-Reply-To: <8a192297-1867-4d97-bcdc-9efad20e9c8f@cesnet.cz>
On Wed, 10 Jul 2024 07:16:58 +0200
Kamil Vojanec <vojanec@cesnet.cz> wrote:
> Hi,
>
> > I don't find the 'direct' mode in latest Linux. Do you have a plan to
> > do this in Linux
> No, I was not planning on any Linux kernel contributions.
> > IIUC, the 'direct' mode just to let the packets from one port send out
> > at the same port, right?
> > If it is, why do you introduce this new mode? It doesn't seem to have
> > anything to do with bonding.
> Indeed, the base functionality is to forward packets to the same port
> they were received on. The main use-case is to allow applications use
> one aggregated (bonding) port ensure that packet forwarding is always
> the same.
>
> I find it a lot simpler to use a bonding port whenever I have an
> application that uses multiple ports. It means I don't have to
> configure, start and stop all the ports; the bonding PMD is a perfect
> abstraction for that.
>
> Kamil
There is overlap between bonding and bridging especially when used as leaf.
This use case sounds like a new driver, rather than dog piling more features
on already complex bridge device. Maybe a new simple bridge PMD would
be more appropriate.
Alternatively, the user transmit policy callback could be an option?
next prev parent reply other threads:[~2024-12-03 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 12:27 Kamil Vojanec
2024-04-12 12:27 ` [PATCH v2 2/2] doc/prog_guide: document " Kamil Vojanec
2024-07-05 11:27 ` [PATCH v2 1/2] net/bonding: introduce " Ferruh Yigit
2024-12-04 22:21 ` Stephen Hemminger
2024-07-10 3:49 ` lihuisong (C)
2024-07-10 5:16 ` Kamil Vojanec
2024-12-03 18:18 ` Stephen Hemminger [this message]
2024-12-12 18:07 ` Stephen Hemminger
2024-12-13 2:37 ` lihuisong (C)
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=20241203101846.4eb39fb9@hermes.local \
--to=stephen@networkplumber.org \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=humin29@huawei.com \
--cc=lihuisong@huawei.com \
--cc=vojanec@cesnet.cz \
/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).