From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Declan Doherty <declan.doherty@intel.com>, dev@dpdk.org
Cc: Keith Wiles <keith.wiles@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/bond: burst mode hash calculation
Date: Wed, 6 Dec 2017 17:42:29 -0800 [thread overview]
Message-ID: <b119699f-580a-1553-6d24-25b4743dd81b@intel.com> (raw)
In-Reply-To: <20171201000405.27870-1-declan.doherty@intel.com>
On 11/30/2017 4:04 PM, Declan Doherty wrote:
> change the xmit_hash functions to handle bursts of packet instead of
> packet at a time. Updating effect tx_burst functions.
>
> Signed-off-by: Declan Doherty <declan.doherty@intel.com>
> Signed-off-by: Keith Wiles <keith.wiles@intel.com>
Hi Declan,
Your other patch [1] conflicts with this one, can you please rebase this one on
top of next-net?
[1]
d8f42bd5f407 ("net/bonding: do not drop LACPDUs on slaves Tx failure")
next prev parent reply other threads:[~2017-12-07 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 0:04 Declan Doherty
2017-12-07 1:42 ` Ferruh Yigit [this message]
2018-01-09 11:34 ` [dpdk-dev] [PATCH v2] " Declan Doherty
2018-01-10 20:39 ` Ferruh Yigit
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=b119699f-580a-1553-6d24-25b4743dd81b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@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).