DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v7 1/1] bond: add mode 4 support v7
Date: Thu, 27 Nov 2014 19:09:20 +0100	[thread overview]
Message-ID: <1503684.yXJvT1DJi7@xps13> (raw)
In-Reply-To: <1417111270-12792-2-git-send-email-michalx.k.jastrzebski@intel.com>

2014-11-27 18:01, Michal Jastrzebski:
> From: Pawel Wodkowski <pawelx.wodkowski@intel.com>
> 
> This patch set add support for dynamic link aggregation (mode 4) to the
> librte_pmd_bond library. This mode provides auto negotiation/configuration 
> of peers and well as link status changes monitoring using out of band 
> LACP (link aggregation control protocol) messages. For further details of
> LACP specification see the IEEE 802.3ad/802.1AX standards. It is also
> described here
> https://www.kernel.org/doc/Documentation/networking/bonding.txt.
> 
> In this implementation we have an array of mode 4 settings for each slave.
> There is also assumption that for every port is one aggregator (it might
> be unused if better is found).
> 
> Difference in this implementation vs Linux implementation:
> - this implementation it is not directly based on state machines but current
>   state is calculated from actor and partner states (and other things too).
> 
> Some implementation details:
> - during rx burst every packet Is checked if this is LACP or marker packet.
>   If it is LACP frame it is passed to mode 4 logic using slaves rx ring  and 
>   removed from rx buffer before it is returned
> - in tx burst, packets from mode 4 (if any) are injected into each slave.
> - there is a timer running in background to process/produce mode 4 
>   frames form rx/to tx functions.
> 
> Some requirements for this mode:
> - for LACP mode to work rx and tx burst functions must be invoked
>   at least in 100ms intervals (testpmd modified to satisfy this requirement)
> - provided buffer to rx burst should be at least 2x slave count size. This is
>   not needed but might increase performance especially during initial
>   handshake.
> 
> Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com>

I guess it is acked by Declan?

-- 
Thomas

  reply	other threads:[~2014-11-27 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 18:01 [dpdk-dev] [PATCH v7 0/1] " Michal Jastrzebski
2014-11-27 18:01 ` [dpdk-dev] [PATCH v7 1/1] " Michal Jastrzebski
2014-11-27 18:09   ` Thomas Monjalon [this message]
2014-11-27 18:13     ` Jastrzebski, MichalX K
2014-11-27 20:25       ` Thomas Monjalon

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=1503684.yXJvT1DJi7@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=michalx.k.jastrzebski@intel.com \
    /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).