From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hyong Youb Kim <hyonkim@cisco.com>
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>,
Dirk-Holger Lenz <dirk.lenz@ng4t.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] net/enic: fix multi-process isseus
Date: Thu, 10 Oct 2019 12:39:13 +0100 [thread overview]
Message-ID: <b542f515-83ed-34f8-2d83-3fd1efa23c6a@intel.com> (raw)
In-Reply-To: <20190906065020.21206-1-hyonkim@cisco.com>
On 9/6/2019 7:50 AM, Hyong Youb Kim wrote:
> This series fixes a few multi-process issues, mainly discovered by
> Dirk-Holger Lenz. They manifest clearly when primary and secondary
> processes use different executable images (hence different rte_eth_dev
> addresses and so on).
>
> Dirk has tested this series, and his app works fine. Below is the
> original email thread.
> http://mails.dpdk.org/archives/dev/2019-August/141560.html
>
> This series replaces the earlier one.
> http://patches.dpdk.org/patch/58033/
>
> Thanks.
> -Hyong
>
> Hyong Youb Kim (3):
> net/enic: restrict several handlers to primary process
> net/enic: fix two issues in probe for secondary process
> net/enic: fix crash in secondary process
Series applied to dpdk-next-net/master, except 1/3.
Change requested for 1/3.
prev parent reply other threads:[~2019-10-10 11:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 6:50 Hyong Youb Kim
2019-09-06 6:50 ` [dpdk-dev] [PATCH 1/3] net/enic: restrict several handlers to primary process Hyong Youb Kim
2019-10-09 8:01 ` Ferruh Yigit
2019-10-09 8:48 ` Hyong Youb Kim (hyonkim)
2019-10-09 9:28 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-10-09 9:38 ` Hyong Youb Kim (hyonkim)
2019-10-09 17:17 ` Ferruh Yigit
2019-09-06 6:50 ` [dpdk-dev] [PATCH 2/3] net/enic: fix two issues in probe for secondary process Hyong Youb Kim
2019-09-06 6:50 ` [dpdk-dev] [PATCH 3/3] net/enic: fix crash in " Hyong Youb Kim
2019-10-10 11:39 ` Ferruh Yigit [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=b542f515-83ed-34f8-2d83-3fd1efa23c6a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=dirk.lenz@ng4t.com \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).