RE: [PATCH net-next] netvsc: Use the new in-place consumption APIs in the rx path

2016-07-01 Thread KY Srinivasan
onical.com; jasow...@redhat.com; > leann.ogasaw...@canonical.com > Subject: RE: [PATCH net-next] netvsc: Use the new in-place consumption APIs in > the rx path > > > > > -Original Message- > > From: Linus Torvalds [mailto:torva...@linux-foundation.org] > > Sen

RE: [PATCH net-next] netvsc: Use the new in-place consumption APIs in the rx path

2016-06-09 Thread KY Srinivasan
...@aepfle.de; > a...@canonical.com; jasow...@redhat.com; > leann.ogasaw...@canonical.com > Subject: Re: [PATCH net-next] netvsc: Use the new in-place consumption APIs in > the rx path > > Srinivasan, > > these are all sent through linuxonhyperv.com, and fail DMARC because > they h

Re: [PATCH net-next] netvsc: Use the new in-place consumption APIs in the rx path

2016-06-09 Thread Linus Torvalds
Srinivasan, these are all sent through linuxonhyperv.com, and fail DMARC because they have a microsoft.com address but no valid DKIM. Please fix your email setup. You need to go through the real microsoft smtp servers if you use a microsoft.com address. Or you need to get linuxonhyperv.com fixe

[PATCH net-next] netvsc: Use the new in-place consumption APIs in the rx path

2016-06-09 Thread K. Y. Srinivasan
Use the new APIs for eliminating a copy on the receive path. These new APIs also help in minimizing the number of memory barriers we end up issuing (in the ringbuffer code) since we can better control when we want to expose the ring state to the host. Signed-off-by: K. Y. Srinivasan Reviewed-by: