From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
jerin.jacob@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH] event/sw: fix hashing of flow on ordered ingress
Date: Thu, 20 Apr 2017 00:24:11 +0200 [thread overview]
Message-ID: <3552049.GAP3nhyey5@xps> (raw)
In-Reply-To: <20170413123131.GA42252@bricha3-MOBL3.ger.corp.intel.com>
13/04/2017 14:31, Bruce Richardson:
> On Mon, Apr 10, 2017 at 04:56:43PM +0100, Harry van Haaren wrote:
> > The flow id of packets was not being hashed on ingress
> > on an ordered queue. Fix by applying same hashing as is
> > applied in the atomic queue case. The hashing itself is
> > broken out into a macro to avoid duplication of code.
> >
> > Fixes: 617995dfc5b2 ("event/sw: add scheduling logic")
> >
> > Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> > ---
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-04-19 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:56 Harry van Haaren
2017-04-13 12:31 ` Bruce Richardson
2017-04-19 22:24 ` Thomas Monjalon [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=3552049.GAP3nhyey5@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerin.jacob@caviumnetworks.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).