[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c7fe8f6655564fcf924521d01d3fa95a@DFM-DB3MBX15-06.exchange.corp.microsoft.com>
Date: Wed, 26 Mar 2014 12:31:24 +0000
From: Haiyang Zhang <haiyangz@...rosoft.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: David Miller <davem@...emloft.net>,
"olaf@...fle.de" <olaf@...fle.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"driverdev-devel@...uxdriverproject.org"
<driverdev-devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH net-next,v4] hyperv: Add support for virtual Receive
Side Scaling (vRSS)
> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Tuesday, March 25, 2014 11:50 PM
> To: Haiyang Zhang
> Cc: David Miller; olaf@...fle.de; netdev@...r.kernel.org;
> jasowang@...hat.com; driverdev-devel@...uxdriverproject.org; linux-
> kernel@...r.kernel.org
> Subject: Re: [PATCH net-next,v4] hyperv: Add support for virtual Receive
> Side Scaling (vRSS)
>
> On Wed, Mar 26, 2014 at 03:23:47AM +0000, Haiyang Zhang wrote:
> >
> >
> > > -----Original Message-----
> > > From: David Miller [mailto:davem@...emloft.net]
> > > Sent: Tuesday, March 25, 2014 8:47 PM
> > > To: Haiyang Zhang
> > > Cc: netdev@...r.kernel.org; KY Srinivasan; olaf@...fle.de;
> > > jasowang@...hat.com; linux-kernel@...r.kernel.org; driverdev-
> > > devel@...uxdriverproject.org
> > > Subject: Re: [PATCH net-next,v4] hyperv: Add support for virtual
> Receive
> > > Side Scaling (vRSS)
> > >
> > > From: David Miller <davem@...emloft.net>
> > > Date: Tue, 25 Mar 2014 20:43:43 -0400 (EDT)
> > >
> > > > From: Haiyang Zhang <haiyangz@...rosoft.com>
> > > > Date: Tue, 25 Mar 2014 20:37:43 +0000
> > > >
> > > >> Do we know when the dependency (commit: 8a7206a89f) will be
> merged
> > > >> into net-next tree?
> > > >
> > > > You're really not very patient, to say the least.
> > > >
> > > > It's done now and I'm working to integrate your patch.
> > > >
> > > > That patch has been in under review state in patchwork, which
> means
> > > > that I will get to it at some point, so you don't need to worry
> about
> > > > it any more than any other patch you might submit.
> > > >
> > > > The whole reason patchwork exists is so that people don't have to
> > > > ask.
> > >
> > > And actually, this dependency "8a7206a89f" commit doesn't exist
> > > in the 'net' tree at all. I just merged Linus's tree into 'net'
> > > and it doesn't exist there either.
> > >
> > > So this patch still doesn't compile.
> > >
> > > I'm tossing it from patchwork until you sort this out.
> >
> > Dave,
> >
> > Thank you for the efforts.
> > The commit is in the linux-next tree. You can see it from this link:
> > http://git.kernel.org/cgit/linux/kernel/git/next/linux-
> next.git/commit/?id=8a7206a89f85c8439561b0eff85bb9440a2e97a9
> > And, here is the commit log:
> >
> > author
> > K. Y. Srinivasan <kys@...rosoft.com> 2014-02-03 20:42:45 (GMT)
> > committer
> > Greg Kroah-Hartman <gregkh@...uxfoundation.org> 2014-02-07 23:22:40
> (GMT)
> > commit
> > 8a7206a89f85c8439561b0eff85bb9440a2e97a9 (patch)
> > tree
> > 61f763919607368481ac128f56416df1f49cd187
> > parent
> > 011a7c3cc3aa60c7ea6bb49d847e80a299ba7b36 (diff)
> >
> > Drivers: hv: vmbus: Support per-channel driver state
> > As we implement Virtual Receive Side Scaling on the networking side
> > (the VRSS patches are currently under review), it will be useful to
> have
> > per-channel state that vmbus drivers can manage. Add support for
> > managing per-channel state.
> >
> > KY:
> > Do you know the original tree this patch was checked into by Greg KH?
> Or,
> > did Greg checked into linux-next tree directly?
>
> No one "checks into the linux-next tree directly".
>
> So your patch relies on a patch in my char-misc tree? Ick, that wasn't
> very wise.
>
> It will just have to wait until the patch goes into 3.15-rc1, as my
> trees are closed, sorry.
Greg,
Thank you for the info. We will wait until KY's earlier patch is merged into
3.15rc1.
In the future, the changes for vmbus or common header used by netvsc driver
should be submitted into net-next tree, correct? So, it can be available quickly
for the subsequent features?
Thanks,
- Haiyang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists