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 v2 0/2] netvsc: event buffer bug fixes
Date: Mon, 13 Aug 2018 08:51:06 -0700	[thread overview]
Message-ID: <20180813155108.6460-1-stephen@networkplumber.org> (raw)

A couple of bugs were introduced by the way the event
buffer is handled.

Stephen Hemminger (2):
  netvsc: fix rte malloc pool corruption
  netvsc: resize event buffer as needed

v2 - split into two patches and fix whitespace

 drivers/net/netvsc/hn_rxtx.c | 49 +++++++++++++++++++++++++-----------
 drivers/net/netvsc/hn_var.h  |  2 +-
 2 files changed, 35 insertions(+), 16 deletions(-)

-- 
2.18.0

             reply	other threads:[~2018-08-13 15:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 15:51 Stephen Hemminger [this message]
2018-08-13 15:51 ` [dpdk-dev] [PATCH v2 1/2] netvsc: fix rte malloc pool corruption Stephen Hemminger
2018-08-13 15:51 ` [dpdk-dev] [PATCH v2 2/2] netvsc: resize event buffer as needed Stephen Hemminger
2018-08-13 17:22   ` Stephen Hemminger

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=20180813155108.6460-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).