From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Doug Ledford <dledford@redhat.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Yishai Hadas <yishaih@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next 0/2] Packet pacing DEVX API
Date: Thu, 5 Mar 2020 14:21:07 +0200 [thread overview]
Message-ID: <20200305122107.GE184088@unreal> (raw)
In-Reply-To: <20200304003303.GA16047@ziepe.ca>
On Tue, Mar 03, 2020 at 08:33:03PM -0400, Jason Gunthorpe wrote:
> On Wed, Feb 19, 2020 at 09:05:16PM +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@mellanox.com>
> >
> > Hi,
> >
> > This series from Yishai extends packet pacing to work over DEVX
> > interface. In first patch, he refactors the mlx5_core internal
> > logic. In second patch, the RDMA APIs are added.
> >
> > Thanks
> >
> > Yishai Hadas (2):
> > net/mlx5: Expose raw packet pacing APIs
> > IB/mlx5: Introduce UAPIs to manage packet pacing
>
> It looks Ok, can you apply this to the shared branch?
Applied to mlx5-next
1326034b3ce7 net/mlx5: Expose raw packet pacing APIs
>
> Thanks,
> Jason
next prev parent reply other threads:[~2020-03-05 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:05 [PATCH rdma-next 0/2] Packet pacing DEVX API Leon Romanovsky
2020-02-19 19:05 ` [PATCH mlx5-next 1/2] net/mlx5: Expose raw packet pacing APIs Leon Romanovsky
2020-02-21 19:04 ` Saeed Mahameed
2020-02-23 8:53 ` Yishai Hadas
2020-02-24 23:32 ` Saeed Mahameed
2020-02-25 7:43 ` Leon Romanovsky
2020-02-19 19:05 ` [PATCH rdma-next 2/2] IB/mlx5: Introduce UAPIs to manage packet pacing Leon Romanovsky
2020-03-04 0:33 ` [PATCH rdma-next 0/2] Packet pacing DEVX API Jason Gunthorpe
2020-03-05 12:21 ` Leon Romanovsky [this message]
2020-03-10 15:44 ` Jason Gunthorpe
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=20200305122107.GE184088@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yishaih@mellanox.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).