> From: David Miller [mailto:da...@davemloft.net] > Sent: Thursday, May 19, 2016 12:13 > To: Dexuan Cui <de...@microsoft.com> > Cc: KY Srinivasan <k...@microsoft.com>; o...@aepfle.de; > gre...@linuxfoundation.org; jasow...@redhat.com; linux- > ker...@vger.kernel.org; j...@perches.com; netdev@vger.kernel.org; > a...@canonical.com; de...@linuxdriverproject.org; Haiyang Zhang > <haiya...@microsoft.com> > Subject: Re: [PATCH v11 net-next 0/1] introduce Hyper-V VM Sockets(hv_sock) > > > I'm travelling and very busy with the merge window. So sorry I won't be able > to think about this for some time.
David, Sure, I understand. Please let me recap my last mail: 1) I'll replace my statically-allocated per-connection "send/recv bufs" with dynamically ones, so no buf is used when there is no traffic. 2) Another kind of bufs i.e., the multi-page "VMBus send/recv ringbuffer", is a must IMO due to the host side's design of the feature: every connection needs its own ringbuffer, which takes several pages (2~3 pages at least. And, 5 pages should suffice for good performance). The ringbuffer can be accessed by the host at any time, so IMO the pages can't be swappable. I understand net-next is closed now. I'm going to post the next version after 4.7-rc1 is out in several weeks. If you could give me some suggestions, I would be definitely happy to take. Thanks! -- Dexuan
