From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH 1/4] netvsc: chimney buffer size error handling
Date: Thu, 23 Aug 2018 08:38:40 -0700 [thread overview]
Message-ID: <20180823083840.4b95e78b@xeon-e3> (raw)
In-Reply-To: <b18ed633-9c31-339e-ce88-fa96699879b9@intel.com>
On Thu, 23 Aug 2018 15:45:17 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 8/9/2018 6:50 PM, Stephen Hemminger wrote:
> > Fix the error handling in setting up transmit buffer.
> > If setting up chimney buffer fails, then it is not connected so
> > no need to send disconnect.
> >
> > Allow for some unused area if full area is not used.
> >
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
>
> subsytem is net/netvsc, so title should be:
> net/netvsc: fix chimney buffer size error handling
>
> Fixes: 4e9c73e96e83 ("net/netvsc: add Hyper-V network device")
> Cc: stable@dpdk.org
>
> Assuming you want patch to be backported.
>
> I will update as above while merging.
There is not a high urgency to back port this. If chimney buffer setup
fails the driver is unusable anyway. It is more of a theoretical error condition.
next prev parent reply other threads:[~2018-08-23 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 17:50 [PATCH 0/4] netvsc performance enhancements Stephen Hemminger
2018-08-09 17:50 ` [PATCH 1/4] netvsc: chimney buffer size error handling Stephen Hemminger
2018-08-23 14:45 ` Ferruh Yigit
2018-08-23 15:38 ` Stephen Hemminger [this message]
2018-08-09 17:50 ` [PATCH 2/4] bus/vmbus: add host latency tuning function Stephen Hemminger
2018-08-23 14:45 ` Ferruh Yigit
2018-08-23 15:40 ` Stephen Hemminger
2018-08-09 17:50 ` [PATCH 3/4] netvsc: set lower host latency Stephen Hemminger
2018-08-09 17:50 ` [PATCH 4/4] netvsc: implement tx_done_cleanup Stephen Hemminger
2018-08-23 14:46 ` Ferruh Yigit
2018-08-23 14:47 ` [PATCH 0/4] netvsc performance enhancements 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=20180823083840.4b95e78b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=sthemmin@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.