DPDK usage discussions
 help / color / mirror / Atom feed
From: "A. Ilchinger" <a.ilchinger@gmx-topmail.de>
To: users@dpdk.org
Subject: [dpdk-users] distributor and flow_id
Date: Sun, 15 Apr 2018 11:41:56 +0200	[thread overview]
Message-ID: <0MFu0Y-1fCbj314Te-00EwMq@mail.gmx.com> (raw)

Hello,
how can I get and set the flow id of packets that are processed by the
distributor? I'd like to go with burst mode, so I only have 15 bits of
flow_id to work with according to the docs. But where do they come
from? My assumption is that its the 5-tuple hash (ip_src, ip_dst,
l4_port_src, l4_port_dst, l4_proto), but do I have to calculate the
hash manually or is there already code in DPDK that does this for me?

The docs also say: "As it does so, it examines the “tag” – stored in
the RSS hash field in the mbuf – for each packet and records what tags
are being processed by each worker."

Does this mean my workers have to set the tag field manually?

Kind regards

                 reply	other threads:[~2018-04-15  9:43 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=0MFu0Y-1fCbj314Te-00EwMq@mail.gmx.com \
    --to=a.ilchinger@gmx-topmail.de \
    --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).