From: Raslan Darawsheh <rasland@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>,
Matan Azrad <matan@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: implement CQ for RxQ using DevX API
Date: Sun, 19 Jul 2020 15:33:27 +0000 [thread overview]
Message-ID: <AM0PR05MB6707A212F9AE6F4375F98D51C27A0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <a113822415c4ee0ea2b6e92dc16b890b0993c9b7.1595152873.git.dekelp@mellanox.com>
Hi,
> -----Original Message-----
> From: Dekel Peled <dekelp@mellanox.com>
> Sent: Sunday, July 19, 2020 2:13 PM
> To: Matan Azrad <matan@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; Raslan Darawsheh <rasland@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [PATCH] net/mlx5: implement CQ for RxQ using DevX API
>
> This patch continues the work to use DevX API for different objects
> creation and management.
> On Rx control path, the RQ, RQT, and TIR objects can already be
> created using DevX API.
> This patch adds the support to create CQ for RxQ using DevX API.
> The corresponding event channel is also created and utilized using
> DevX API.
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> drivers/net/mlx5/linux/mlx5_os.c | 21 ++
> drivers/net/mlx5/mlx5.c | 10 +
> drivers/net/mlx5/mlx5.h | 2 +
> drivers/net/mlx5/mlx5_rxq.c | 422 +++++++++++++++++++++++++++++-
> ---------
> drivers/net/mlx5/mlx5_rxtx.h | 29 ++-
> 5 files changed, 375 insertions(+), 109 deletions(-)
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-07-19 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 11:13 Dekel Peled
2020-07-19 15:33 ` Raslan Darawsheh [this message]
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=AM0PR05MB6707A212F9AE6F4375F98D51C27A0@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=viacheslavo@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).