All of lore.kernel.org
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Asaf Penso <asafp@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	Matan Azrad <matan@nvidia.com>,
	Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add information for Rx burst functions in mlx5
Date: Mon, 23 Nov 2020 08:14:19 +0000	[thread overview]
Message-ID: <MWHPR12MB1501C94A474F9DD511C114ADDFFC0@MWHPR12MB1501.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1606118685-32134-1-git-send-email-asafp@nvidia.com>

> -----Original Message-----
> From: Asaf Penso <asafp@nvidia.com>
> Sent: Monday, November 23, 2020 10:05
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Raslan
> Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v3] doc: add information for Rx burst functions in mlx5
> 
> mlx5 pmd supports various rx_burst functions.
> Each function is enabled differently and supports different features.
> 
> Add more comprehensive information about each function.
> 
> Signed-off-by: Asaf Penso <asafp@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>


  reply	other threads:[~2020-11-23  8:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22 12:35 [dpdk-dev] [PATCH] doc: add information for Rx burst functions in mlx5 Asaf Penso
2020-11-23  7:17 ` Slava Ovsiienko
2020-11-23  7:56 ` [dpdk-dev] [PATCH v2] " Asaf Penso
2020-11-23  8:04   ` [dpdk-dev] [PATCH v3] " Asaf Penso
2020-11-23  8:14     ` Slava Ovsiienko [this message]
2020-11-24  7:44     ` [dpdk-dev] [PATCH v4] " Asaf Penso
2020-11-26 23:55       ` [dpdk-dev] [PATCH v5] doc: add Rx functions limitations in mlx5 guide Thomas Monjalon
2020-11-27  0:04         ` Thomas Monjalon

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=MWHPR12MB1501C94A474F9DD511C114ADDFFC0@MWHPR12MB1501.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=asafp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.