Re: netvsc NAPI

2017-02-23 Thread Stephen Hemminger
On Thu, 23 Feb 2017 18:24:06 -0500 (EST) David Miller wrote: > From: Stephen Hemminger > Date: Wed, 22 Feb 2017 09:33:16 -0800 > > > NAPI for netvsc is ready but the merge coordination is a nuisance. > > > > Since netvsc NAPI support requires other changes

Re: netvsc NAPI

2017-02-23 Thread David Miller
From: Stephen Hemminger Date: Wed, 22 Feb 2017 09:33:16 -0800 > NAPI for netvsc is ready but the merge coordination is a nuisance. > > Since netvsc NAPI support requires other changes that are proceeding through > GregKH's char-misc tree. I would like to send the two patc

netvsc NAPI

2017-02-22 Thread Stephen Hemminger
NAPI for netvsc is ready but the merge coordination is a nuisance. Since netvsc NAPI support requires other changes that are proceeding through GregKH's char-misc tree. I would like to send the two patches after current net-next and char-misc-next are merged into Linus's tree. Need t

Re: netvsc NAPI patch process

2017-01-27 Thread Stephen Hemminger
On Fri, 27 Jan 2017 08:54:06 +0100 Greg KH wrote: > On Thu, Jan 26, 2017 at 01:06:46PM -0500, David Miller wrote: > > From: Stephen Hemminger > > Date: Thu, 26 Jan 2017 10:04:05 -0800 > > > > > I have a working set of patches to enable NAPI in the netvsc driver. > > > The problem is that it r

Re: netvsc NAPI patch process

2017-01-27 Thread Greg KH
On Fri, Jan 27, 2017 at 09:39:53AM -0800, Stephen Hemminger wrote: > On Fri, 27 Jan 2017 08:54:06 +0100 > Greg KH wrote: > > > On Thu, Jan 26, 2017 at 01:06:46PM -0500, David Miller wrote: > > > From: Stephen Hemminger > > > Date: Thu, 26 Jan 2017 10:04:05 -0800 > > > > > > > I have a working

Re: netvsc NAPI patch process

2017-01-26 Thread Greg KH
On Thu, Jan 26, 2017 at 01:06:46PM -0500, David Miller wrote: > From: Stephen Hemminger > Date: Thu, 26 Jan 2017 10:04:05 -0800 > > > I have a working set of patches to enable NAPI in the netvsc driver. > > The problem is that it requires a set of patches to vmbus layer as well. > > Since vmbus p

Re: netvsc NAPI patch process

2017-01-26 Thread David Miller
From: KY Srinivasan Date: Thu, 26 Jan 2017 20:46:40 + > In the past, we have done this in two stages - get the supporting > vmbus patches into Greg's tree first and in the next merge cycle get > the netvsc patches in. Why not continue to do what we have done in > the past to address cross-tre

RE: netvsc NAPI patch process

2017-01-26 Thread KY Srinivasan
> -Original Message- > From: Stephen Hemminger [mailto:step...@networkplumber.org] > Sent: Thursday, January 26, 2017 10:04 AM > To: da...@davemloft.net; KY Srinivasan ; Greg KH > > Cc: netdev@vger.kernel.org > Subject: netvsc NAPI patch process > > I have

Re: netvsc NAPI patch process

2017-01-26 Thread David Miller
From: Stephen Hemminger Date: Thu, 26 Jan 2017 10:04:05 -0800 > I have a working set of patches to enable NAPI in the netvsc driver. > The problem is that it requires a set of patches to vmbus layer as well. > Since vmbus patches have been going through char-misc-next tree rather > than net-next,

netvsc NAPI patch process

2017-01-26 Thread Stephen Hemminger
I have a working set of patches to enable NAPI in the netvsc driver. The problem is that it requires a set of patches to vmbus layer as well. Since vmbus patches have been going through char-misc-next tree rather than net-next, it is difficult to stage these. How about if I send the vmbus patches