From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Asaf Penso <asafp@nvidia.com>,
"carsten.andrich@tu-ilmenau.de" <carsten.andrich@tu-ilmenau.de>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] doc: fix supported feature table in mlx5 guide
Date: Wed, 3 Feb 2021 14:18:48 +0000 [thread overview]
Message-ID: <DM6PR12MB2748EC94EA4BF28DC8535E3BCFB49@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210202142732.14492-1-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Sent: Tuesday, February 2, 2021 4:28 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; NBU-Contact-Thomas
> Monjalon <thomas@monjalon.net>; Asaf Penso <asafp@nvidia.com>;
> carsten.andrich@tu-ilmenau.de; stable@dpdk.org
> Subject: [PATCH] doc: fix supported feature table in mlx5 guide
>
> The fixes:
I'd replace this with something like following if it's OK with you and I can do it during integration,
This sets the correct minimal requirements for these feature:
>
> - Buffer Split offload is supported/verified on ConnectX-5
> - Tx scheduling requires ConnectX-6DX and depends on firmware version
>
> Fixes: cb7b0c24c835 ("doc: update hardware offloads support in mlx5 guide")
> Cc: stable@dpdk.org
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> doc/guides/nics/mlx5.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
[..]
Kindest regards
Raslan Darawsheh
next prev parent reply other threads:[~2021-02-03 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 14:27 Viacheslav Ovsiienko
2021-02-02 15:37 ` Asaf Penso
2021-02-03 14:18 ` Raslan Darawsheh [this message]
2021-02-03 14:25 ` Slava Ovsiienko
2021-02-03 14:27 ` Raslan Darawsheh
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=DM6PR12MB2748EC94EA4BF28DC8535E3BCFB49@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=asafp@nvidia.com \
--cc=carsten.andrich@tu-ilmenau.de \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@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).