DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: [PATCH v1] net/mlx5: adapt parse graph header length limitation
Date: Mon, 19 Jun 2023 15:02:27 +0000	[thread overview]
Message-ID: <BYAPR12MB3078C618FE02AD3545B280BCCF5FA@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230612080408.2029533-1-rongweil@nvidia.com>

Hi,

> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Monday, June 12, 2023 11:04 AM
> To: dev@dpdk.org; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> <thomas@monjalon.net>
> Subject: [PATCH v1] net/mlx5: adapt parse graph header length limitation
> 
> Firmware exports the parse graph header length capability via hca_attr and the
> current value is 6.
> The user must specify the header length field via field_size.
> Field size implies the mask implicitly as 2^field_size-1
> 
> 1. If field_size is bigger than 6, PMD needs to add an extra offset internally, let
> HW only parses the 6 LSBs as length.
>            length
> |--------|--------|--------|--------|
> The actual header length offset 8 doesn't work well with new firmware, only
> the bits 8-13 are read and parsed as a length field.
> Need to change the offset to 10 (8 + 2) internally. Field mask can't be bigger
> than 0x3F (2^6-1).
> 
> 2. If filed_size is smaller that 6, PMD needs to subtract an offset to fit 6 bits
> exactly.
>          length
> |--------|----|------------|--------|
> The actual header length offset 8 doesn't work well with new firmware
> because firmware will read two more bits from the next field.
> Need to change the offset to 6 (8 -2) internally.
> 
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2023-06-19 15:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  8:04 Rongwei Liu
2023-06-19 15:02 ` 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=BYAPR12MB3078C618FE02AD3545B280BCCF5FA@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rongweil@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --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).