DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, hengx.ding@intel.com, qian.q.xu@intel.com,
	konstantin.ananyev@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples: fix duplicated lpm6 name
Date: Wed, 15 Jun 2016 16:30:24 +0200	[thread overview]
Message-ID: <1552546.eUD0UMXYVF@xps13> (raw)
In-Reply-To: <1465810983-11324-1-git-send-email-olivier.matz@6wind.com>

2016-06-13 11:43, Olivier Matz:
> When starting the ip_fragmentation or ip_reassembly example
> on several sockets, it fails.
> 
> The name of the lpm6 table is the same on every socket,
> resulting in a table creation failure (-EEXIST). The failure
> appeared after:
> commit f82f705b635d ("lpm: fix allocation of an existing object")
> 
> Indeed, before this commit the returned value when the existing
> table, which was probably a bug in that case: one table for 2
> sockets for lpm6, and one per socket for lpm.
> 
> Fixes: 74de12b7b63a ("examples/ip_fragmentation: overhaul")
> Fixes: b84fb4cb88ff ("examples/ip_reassembly: overhaul")
> Reported-by: Ding Heng <hengx.ding@intel.com>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>

Applied, thanks

      reply	other threads:[~2016-06-15 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13  7:41 [dpdk-dev] run ip_fragmentation with cores in different socket will cause core dump Ding, HengX
2016-06-13  8:46 ` Olivier Matz
2016-06-13  9:43   ` [dpdk-dev] [PATCH] examples: fix duplicated lpm6 name Olivier Matz
2016-06-15 14:30     ` 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=1552546.eUD0UMXYVF@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=hengx.ding@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=qian.q.xu@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).