From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Subject: [dpdk-stable] FW: [dpdk-dev] [PATCH] hash: fix incorrect bucket size usage
Date: Wed, 12 Oct 2016 15:32:57 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973CA08334@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <7689701.7CCK6hcHEJ@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Wednesday, October 12, 2016 8:04 AM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org; Richardson, Bruce
> Subject: Re: [dpdk-dev] [PATCH] hash: fix incorrect bucket size usage
>
> 2016-10-12 02:26, Pablo de Lara:
> > Multiwriter insert function was using a fixed value for
> > the bucket size, instead of using the
> > RTE_HASH_BUCKET_ENTRIES macro, which value was changed
> > recently (making it inconsistent in this case).
> >
> > Fixes: be856325cba3 ("hash: add scalable multi-writer insertion with Intel
> TSX")
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> Applied, thanks
This patch should be merged in the stable repo.
Thanks,
Pablo
parent reply other threads:[~2016-10-12 15:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <7689701.7CCK6hcHEJ@xps13>]
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=E115CCD9D858EF4F90C690B0DCB4D8973CA08334@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=stable@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).