From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>
Cc: Leon Romanovsky <leon@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Saeed Mahameed <saeedm@nvidia.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: mlx5-next 2023-01-24 V2
Date: Thu, 2 Feb 2023 10:30:04 -0800 [thread overview]
Message-ID: <20230202103004.26ab6ae9@kernel.org> (raw)
In-Reply-To: <Y9v93cy0s9HULnWq@x130>
On Thu, 2 Feb 2023 10:15:57 -0800 Saeed Mahameed wrote:
> It's a reality that mlx5_core is serving both netdev and rdma, it's not
> about who has the keys for approving, it's that the fact the mlx5_core is
> not just a netdev driver
Nah, nah, nah, don't play with me. You put in "full IPsec offload"
with little netdev use, then start pushing RDMA IPsec patches.
Don't make it sound like netdev and rdma are separate entities which
just share the HW when you're using APIs of one to configure the other.
If RDMA invented its own API for IPsec without touching xfrm, we would
not be having this conversation. That'd be fine by me.
You used our APIs to make your proprietary thing easier to integrate and
configure - now you have to find someone who will pull the PR and still
sleep at night. Not me.
next prev parent reply other threads:[~2023-02-02 18:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 23:08 pull-request: mlx5-next 2023-01-24 V2 Saeed Mahameed
2023-02-02 7:46 ` Leon Romanovsky
2023-02-02 17:13 ` Jakub Kicinski
2023-02-02 17:14 ` Jason Gunthorpe
2023-02-02 17:25 ` Jakub Kicinski
2023-02-02 17:44 ` Jason Gunthorpe
2023-02-02 17:54 ` Jakub Kicinski
2023-02-02 18:03 ` Leon Romanovsky
2023-02-02 18:15 ` Saeed Mahameed
2023-02-02 18:30 ` Jakub Kicinski [this message]
2023-02-03 20:05 ` Saeed Mahameed
2023-02-03 21:14 ` Jakub Kicinski
2023-02-04 0:18 ` Jason Gunthorpe
2023-02-04 1:45 ` Jakub Kicinski
2023-02-06 14:58 ` Jason Gunthorpe
2023-02-07 0:38 ` Jakub Kicinski
2023-02-07 19:52 ` Jason Gunthorpe
2023-02-07 22:03 ` Jakub Kicinski
2023-02-08 9:17 ` Leon Romanovsky
2023-02-08 16:13 ` Jason Gunthorpe
2023-02-08 23:19 ` Jakub Kicinski
2023-02-09 0:27 ` Jason Gunthorpe
2023-02-09 0:48 ` Jakub Kicinski
2023-02-09 0:59 ` Jason Gunthorpe
2023-02-09 1:16 ` Jakub Kicinski
2023-02-10 17:15 ` Jason Gunthorpe
2023-02-09 0:36 ` Saeed Mahameed
2023-02-09 0:52 ` Jakub Kicinski
2023-02-04 0:47 ` Saeed Mahameed
2023-02-04 1:57 ` Jakub Kicinski
2023-02-05 10:26 ` Leon Romanovsky
2023-02-02 18:07 ` Leon Romanovsky
2023-02-03 20:14 ` Saeed Mahameed
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=20230202103004.26ab6ae9@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.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).