From: dirk <dirk.lenz@ng4t.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/1] net/enic: enic driver doesn't work with 2nd process
Date: Tue, 27 Aug 2019 11:02:47 +0200 [thread overview]
Message-ID: <20190827090248.6185-1-dirk.lenz@ng4t.com> (raw)
dirk (1):
net/enic: enic driver doesn't work with 2nd process. the problem is that the
private data structure enic uses pointers to rte_eth_dev and rte_pci_device
which are overwritten when a 2nd process starts using this device.
given patch removes these two pointers from the private data and uses the
correct pointers. For us the given patch works fine on a cisco rack.
(we used three processes working concurrently)
drivers/net/enic/enic.h | 36 ++++---
drivers/net/enic/enic_clsf.c | 5 +-
drivers/net/enic/enic_ethdev.c | 79 ++++++---------
drivers/net/enic/enic_main.c | 177 +++++++++++++++++++---------------
drivers/net/enic/enic_res.c | 7 +-
drivers/net/enic/enic_res.h | 6 +-
drivers/net/enic/enic_rxtx_vec_avx2.c | 5 +-
7 files changed, 156 insertions(+), 159 deletions(-)
--
2.15.1
next reply other threads:[~2019-08-27 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 9:02 dirk [this message]
2019-08-27 9:02 ` [dpdk-dev] [PATCH 1/1] " dirk
2019-09-02 6:40 ` Hyong Youb Kim (hyonkim)
-- strict thread matches above, loose matches on Subject: below --
2019-08-27 8:33 [dpdk-dev] [PATCH 0/1] " dirk
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=20190827090248.6185-1-dirk.lenz@ng4t.com \
--to=dirk.lenz@ng4t.com \
--cc=dev@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).