From: David Miller <davem@redhat.com>
To: kys@microsoft.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
jasowang@redhat.com
Subject: Re: [PATCH V3 0/2 net-next] hyperv: Enable batched notification
Date: Tue, 17 Mar 2015 15:23:24 -0400 (EDT) [thread overview]
Message-ID: <20150317.152324.744727347577991569.davem@redhat.com> (raw)
In-Reply-To: <1426608145-14139-1-git-send-email-kys@microsoft.com>
From: "K. Y. Srinivasan" <kys@microsoft.com>
Date: Tue, 17 Mar 2015 09:02:25 -0700
> Take into consideration the xmit_more flag in skb to decide if we should
> notify the host as we place packets in VMBUS.
>
> The VMBUS API that would give us this control is already in Greg's tree, in this
> patch-set, that API is exported so it can be used in the netvsc driver. Greg has
> acked this export.
>
> In this version of the patch-set, the patch to address the vmbus signalling
> fix is not included here; that patch will be taken through Greg's tree.
> I have also gotten rid of an unnecessary local variable in start_xmit()
> function based on feedback from Jason Wang <jasowang@redhat.com>.
This patch set does not apply to net-next at all.
next prev parent reply other threads:[~2015-03-17 19:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 16:02 [PATCH V3 0/2 net-next] hyperv: Enable batched notification K. Y. Srinivasan
2015-03-17 16:02 ` [PATCH V3 1/2 net-next] Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl() K. Y. Srinivasan
2015-03-17 16:02 ` [PATCH V3 2/2 net-next] hyperv: Support batched notification K. Y. Srinivasan
2015-03-18 3:08 ` Jason Wang
2015-03-19 16:53 ` KY Srinivasan
[not found] ` <BY2PR0301MB07114336B35924D353108197A0010@BY2PR0301MB0711.namprd03.prod.out look.com>
2015-03-20 5:57 ` Jason Wang
2015-03-20 14:01 ` KY Srinivasan
2015-03-17 19:23 ` David Miller [this message]
2015-03-17 19:26 ` [PATCH V3 0/2 net-next] hyperv: Enable " KY Srinivasan
2015-03-17 20:07 ` KY Srinivasan
2015-03-17 21:37 ` David Miller
2015-03-17 21:39 ` KY Srinivasan
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=20150317.152324.744727347577991569.davem@redhat.com \
--to=davem@redhat.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/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).