DPDK usage discussions
 help / color / mirror / Atom feed
From: Vincent <techburgher@gmail.com>
To: users@dpdk.org
Subject: DPDK lacp bonding - xmit hash
Date: Wed, 18 Sep 2024 18:20:53 -0400	[thread overview]
Message-ID: <CAMj4T0zFKmX0Jv_mCy1=n=MKtztySygXnjCOnUNzOeVWp1JmQA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

What determines what xmit_hash_policy DPDK will use for LACP bonded links?
Does it not respect the value specified by
/sys/class/net/<INTERFACE>/bonding/xmit_hash_policy?

Based on testing, it seems like layer2, or layer3+4 hashing is being done,
but the behavior is random, and seems to not necessarily reflect the
current value specified by
/sys/class/net/<INTERFACE>/bonding/xmit_hash_policy.

Thank you,

Vincent

[-- Attachment #2: Type: text/html, Size: 509 bytes --]

             reply	other threads:[~2024-09-18 22:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 22:20 Vincent [this message]
2024-09-18 23:36 ` Stephen Hemminger

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='CAMj4T0zFKmX0Jv_mCy1=n=MKtztySygXnjCOnUNzOeVWp1JmQA@mail.gmail.com' \
    --to=techburgher@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).