[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6ce5204-90ca-0095-a50b-a0306f61592d@gmail.com>
Date: Wed, 15 Jan 2020 10:34:04 -0700
From: David Ahern <dsahern@...il.com>
To: Jiri Pirko <jiri@...nulli.us>,
Leon Romanovsky <leonro@...lanox.com>
Cc: Maor Gottlieb <maorg@...lanox.com>,
"j.vosburgh@...il.com" <j.vosburgh@...il.com>,
"vfalico@...il.com" <vfalico@...il.com>,
"andy@...yhouse.net" <andy@...yhouse.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Saeed Mahameed <saeedm@...lanox.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Jiri Pirko <jiri@...lanox.com>,
Alex Rosenbaum <alexr@...lanox.com>,
"davem@...emloft.net" <davem@...emloft.net>,
Mark Zhang <markz@...lanox.com>,
Parav Pandit <parav@...lanox.com>
Subject: Re: Expose bond_xmit_hash function
On 1/15/20 9:48 AM, Jiri Pirko wrote:
>>
>> Right now, we have one of two options:
>> 1. One-to-one copy/paste of that bond_xmit function to RDMA.
>> 2. Add EXPORT_SYMBOL and call from RDMA.
>>
>> Do you have another solution to our undesire to do copy/paste in mind?
>
> I presented it in this thread.
>
Something similar is needed for xdp and not necessarily tied to a
specific bond mode. Some time back I was using this as a prototype:
https://github.com/dsahern/linux/commit/2714abc1e629613e3485b7aa860fa3096e273cb2
It is incomplete, but shows the intent - exporting bond_egress_slave for
use by other code to take a bond device and return an egress leg.
Powered by blists - more mailing lists