[ovs-dev] [PATCH 1/2] datapath-windows: don't map output buffer in OVS_IOCTL_WRITE

Joe Stringer joe at ovn.org
Wed May 25 17:34:36 UTC 2016


On 19 May 2016 at 23:48, Paul Boca <pboca at cloudbasesolutions.com> wrote:
> Acked-by: Paul-Daniel Boca <pboca at cloudbasesolutions.com>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces at openvswitch.org] On Behalf Of Nithin Raju
>> Sent: Friday, May 20, 2016 1:32 AM
>> To: dev at openvswitch.org
>> Subject: [ovs-dev] [PATCH 1/2] datapath-windows: don't map output buffer in
>> OVS_IOCTL_WRITE
>>
>> The contract of OVS_IOCTL_WRITE is that write operations
>> will not need the output buffer. Only the input buffer
>> will be used in the IRP. So, better to not map the output
>> buffer at all.
>>
>> Signed-off-by: Nithin Raju <nithin at vmware.com>


Thanks, applied



More information about the dev mailing list