DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Raslan Darawsheh <rasland@nvidia.com>, Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: support Flow Tag and Packet Header miniCQEs
Date: Sun, 1 Nov 2020 16:38:31 +0000
Message-ID: <MWHPR12MB1501251E6A7CC674069107D6DF130@MWHPR12MB1501.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201101162739.11148-1-akozyrev@nvidia.com>

> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Sunday, November 1, 2020 18:28
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH v2] net/mlx5: support Flow Tag and Packet Header miniCQEs
> CQE compression allows us to save the PCI bandwidth and improve the
> performance by compressing several CQEs together to a miniCQE.
> But the miniCQE size is only 8 bytes and this limits the ability to successfully
> keep the compression session in case of various traffic patterns.
> The current miniCQE format only keeps the compression session alive in case
> of uniform traffic with the Hash RSS as the only difference.
> There are requests to keep the compression session in case of tagged traffic by
> RTE Flow Mark Id and mixed UDP/TCP and IPv4/IPv6 traffic.
> Add 2 new miniCQE formats in order to achieve the best performance for
> these traffic patterns: Flow Tag and Packet Header miniCQEs.
> The existing rxq_cqe_comp_en devarg is modified to specify the desired
> miniCQE format. Specifying 2 selects Flow Tag format for better compression
> rate in case of RTE Flow Mark traffic.
> Specifying 3 selects Checksum format (existing format for MPRQ).
> Specifying 4 selects L3/L4 Header format for better compression rate in case of
> mixed TCP/UDP and IPv4/IPv6 traffic.
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

  reply	other threads:[~2020-11-01 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28  2:37 [dpdk-dev] [PATCH] " Alexander Kozyrev
2020-11-01 16:27 ` [dpdk-dev] [PATCH v2] " Alexander Kozyrev
2020-11-01 16:38   ` Slava Ovsiienko [this message]
2020-11-01 16:14 Alexander Kozyrev
2020-11-01 23:56 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR12MB1501251E6A7CC674069107D6DF130@MWHPR12MB1501.namprd12.prod.outlook.com \
    --to=viacheslavo@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git