[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY2PR0301MB07115FFD6E62E07CBAB0AED0A0190@BY2PR0301MB0711.namprd03.prod.outlook.com>
Date: Wed, 11 Mar 2015 17:45:02 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Olaf Hering <olaf@...fle.de>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"apw@...onical.com" <apw@...onical.com>,
"jasowang@...hat.com" <jasowang@...hat.com>
Subject: RE: [PATCH 2/2 net-next] hyperv: Support batched notification
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@...fle.de]
> Sent: Wednesday, March 11, 2015 2:24 AM
> To: KY Srinivasan
> Cc: davem@...emloft.net; netdev@...r.kernel.org;
> gregkh@...uxfoundation.org; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; apw@...onical.com; jasowang@...hat.com
> Subject: Re: [PATCH 2/2 net-next] hyperv: Support batched notification
>
> On Tue, Mar 10, K. Y. Srinivasan wrote:
>
> > Optimize notifying the host by deferring notification until there are
> > no more packets to be sent. This will help in batching the requests on
> > the host.
>
> The subjects for the network driver say "hyperv:". But all such changes
> should get "netvsc:" as prefix to make it clear what each single patch is all
> about.
>
> This should be changed for upcoming submissions.
Olaf,
This is the convention that we have used for patches submitted to David's tree. You will see
net-next in the subject line and you can key off of that.
K. Y
>
> Thanks!
>
> Olaf
Powered by blists - more mailing lists