DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alexander Kozyrev <akozyrev@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [RFC] net/mlx5: Flow mark ID and L3/L4 header CQE compression
Date: Fri, 4 Sep 2020 22:09:57 +0000
Message-ID: <BN7PR12MB270736E884E19ACE23C9DEA5AF2D0@BN7PR12MB2707.namprd12.prod.outlook.com> (raw)

CQE compression reduces PCI bandwidth usage by coalescing and compressing
multiple CQEs into a single zipped CQE. This improves Rx message rate,
especially for small packet traffic.

CQEs must be almost identical to be successfully merged and compressed
together. All the shared data is contained in the Title Compression block,
while the packet size, for example, may differ and stored in the each
compressed CQE independently.

CQE compression doesn't tolerate any other differences except the packet
size and the Checksum/Hash and falls back to the regular CQE scheme in all
other cases.

There is a proposal to include more fields into the CQE compression format
to achieve a better performance in the following scenarios:
1. Different RTE Flow marks associated with Rx traffic.
Having the mark ID as part of the mini-CQE structure allows us to keep
the CQE compression uninterrupted for multiple different RTE flows with
different mark IDs.
2. Mixed TCP/UDP and IPv4/IPv6 traffic.
Adding L3/L4 header type to the mini-CQE format helps with the performance
of the mixed traffic of various TCP/UDP headers and coexistence of IPv4
and IPv6 protocols in one compression session.

                 reply	other threads:[~2020-09-04 22:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BN7PR12MB270736E884E19ACE23C9DEA5AF2D0@BN7PR12MB2707.namprd12.prod.outlook.com \
    --to=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    /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

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 \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


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