DPDK usage discussions
 help / color / mirror / Atom feed
From: Pawel Wodkowski <pawelwod@gmail.com>
To: users@dpdk.org
Subject: Re: Strategy for contiguous packet payload processing using DPDK mbufs
Date: Thu, 28 Jul 2022 11:21:12 +0200	[thread overview]
Message-ID: <b00b1ca0-34c2-cfcc-40ab-73e86a7873d0@gmail.com> (raw)
In-Reply-To: <MW3PR22MB21081B7AE10ECAC571211E18E0979@MW3PR22MB2108.namprd22.prod.outlook.com>

On 27.07.2022 17:03, Filip Matracki wrote:
> What strategy is recommended for a DPDK application that needs to 
> process the payload of network packets in contiguous memory?

1. Don't care about the wasted memory?
2. Reassembly large packets into contiguous memory.
3. Use NIC features to redirect packets to proper RX queues. Small 
packets goes to first queue, medium size to second, large to third. This 
might be tricky and hardware dependent.

-- 
Paweł

      reply	other threads:[~2022-07-28  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 15:03 Filip Matracki
2022-07-28  9:21 ` Pawel Wodkowski [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=b00b1ca0-34c2-cfcc-40ab-73e86a7873d0@gmail.com \
    --to=pawelwod@gmail.com \
    --cc=users@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
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).