netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Maor Gottlieb <maorg@mellanox.com>
Cc: "j.vosburgh@gmail.com" <j.vosburgh@gmail.com>,
	"vfalico@gmail.com" <vfalico@gmail.com>,
	"andy@greyhouse.net" <andy@greyhouse.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Saeed Mahameed <saeedm@mellanox.com>,
	Jason Gunthorpe <jgg@mellanox.com>,
	Leon Romanovsky <leonro@mellanox.com>,
	Jiri Pirko <jiri@mellanox.com>,
	Alex Rosenbaum <alexr@mellanox.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	Mark Zhang <markz@mellanox.com>,
	Parav Pandit <parav@mellanox.com>
Subject: Re: Expose bond_xmit_hash function
Date: Wed, 15 Jan 2020 15:15:35 +0100	[thread overview]
Message-ID: <20200115141535.GT2131@nanopsycho> (raw)
In-Reply-To: <80ad03a2-9926-bf75-d79c-be554c4afaaf@mellanox.com>

Wed, Jan 15, 2020 at 02:04:49PM CET, maorg@mellanox.com wrote:
>
>On 1/15/2020 11:45 AM, Jiri Pirko wrote:
>> Wed, Jan 15, 2020 at 09:01:43AM CET, maorg@mellanox.com wrote:
>>> RDMA over Converged Ethernet (RoCE) is a standard protocol which enables
>>> RDMA’s efficient data transfer over Ethernet networks allowing transport
>>> offload with hardware RDMA engine implementation.
>>> The RoCE v2 protocol exists on top of either the UDP/IPv4 or the
>>> UDP/IPv6 protocol:
>>>
>>> --------------------------------------------------------------
>>> | L2 | L3 | UDP |IB BTH | Payload| ICRC | FCS |
>>> --------------------------------------------------------------
>>>
>>> When a bond LAG netdev is in use, we would like to have the same hash
>>> result for RoCE packets as any other UDP packets, for this purpose we
>>> need to expose the bond_xmit_hash function to external modules.
>>> If no objection, I will push a patch that export this symbol.
>> I don't think it is good idea to do it. It is an internal bond function.
>> it even accepts "struct bonding *bond". Do you plan to push netdev
>> struct as an arg instead? What about team? What about OVS bonding?
>
>No, I am planning to pass the bond struct as an arg. Currently, team 

Hmm, that would be ofcourse wrong, as it is internal bonding driver
structure.


>bonding is not supported in RoCE LAG and I don't see how OVS is related.

Should work for all. OVS is related in a sense that you can do bonding
there too.


>
>>
>> Also, you don't really need a hash, you need a slave that is going to be
>> used for a packet xmit.
>>
>> I think this could work in a generic way:
>>
>> struct net_device *master_xmit_slave_get(struct net_device *master_dev,
>> 					 struct sk_buff *skb);
>
>The suggestion is to put this function in the bond driver and call it 
>instead of bond_xmit_hash? is it still necessary if I have the bond pointer?

No. This should be in a generic code. No direct calls down to bonding
driver please. Or do you want to load bonding module every time your
module loads?

I thinks this can be implemented with ndo with "master_xmit_slave_get()"
as a wrapper. Masters that support this would just implement the ndo.

>

  reply	other threads:[~2020-01-15 14:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  8:01 Expose bond_xmit_hash function Maor Gottlieb
2020-01-15  9:45 ` Jiri Pirko
2020-01-15 13:04   ` Maor Gottlieb
2020-01-15 14:15     ` Jiri Pirko [this message]
2020-01-15 14:33       ` Leon Romanovsky
2020-01-15 16:48         ` Jiri Pirko
2020-01-15 17:34           ` David Ahern
2020-01-15 18:04             ` Jay Vosburgh
2020-01-15 18:12               ` David Ahern
2020-01-15 20:46                 ` Jiri Pirko
2020-01-15 20:58                   ` David Ahern
2020-01-16 14:42       ` Andy Gospodarek
2020-01-16 15:55         ` Maor Gottlieb
2020-01-16 16:00           ` Jay Vosburgh
2020-01-19 14:52             ` Maor Gottlieb
2020-01-20 18:43               ` Jay Vosburgh
2020-01-22  7:53                 ` Maor Gottlieb

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=20200115141535.GT2131@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=alexr@mellanox.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=j.vosburgh@gmail.com \
    --cc=jgg@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=maorg@mellanox.com \
    --cc=markz@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@mellanox.com \
    --cc=saeedm@mellanox.com \
    --cc=vfalico@gmail.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).