DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/2] net/netvsc: fix secondary process issues
Date: Mon, 13 Jan 2020 11:12:37 -0800	[thread overview]
Message-ID: <20200113191239.22750-1-stephen@networkplumber.org> (raw)

First patch is a bug fix for crash in info_get in secondary process.
Second one is modification to prevent similar issues in future.

Stephen Hemminger (2):
  net/netvsc: fix crash in secondary process
  net/netvsc: eliminate numa specific allocation for control messages

 drivers/net/netvsc/hn_ethdev.c | 17 +++++++++--------
 drivers/net/netvsc/hn_rndis.c  | 11 +++++------
 2 files changed, 14 insertions(+), 14 deletions(-)

-- 
2.20.1


             reply	other threads:[~2020-01-13 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 19:12 Stephen Hemminger [this message]
2020-01-13 19:12 ` [dpdk-dev] [PATCH 1/2] net/netvsc: fix crash in secondary process Stephen Hemminger
2020-01-13 19:12 ` [dpdk-dev] [PATCH 2/2] net/netvsc: eliminate numa specific allocation for control messages Stephen Hemminger
2020-01-14 16:51 ` [dpdk-dev] [PATCH 0/2] net/netvsc: fix secondary process issues Ferruh Yigit

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=20200113191239.22750-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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).