Displaying 4 results from an estimated 4 matches for "msghdrs".
Did you mean:
msghdr
2013 May 30
1
updated: kvm networking todo wiki
...#39;t have to complete buffers in order.
What I meant though was for GRO, we don't know how large the received
packet is going to be. Mergable rx buffers lets us allocate a pool of
data for all incoming packets instead of allocating max packet size *
max packets.
recvmmsg expects an array of msghdrs and I presume each needs to be
given a fixed size. So this seems incompatible with mergable rx
buffers.
Regards,
Anthony Liguori
>
>> >
>> > Stefan
2013 May 30
1
updated: kvm networking todo wiki
...#39;t have to complete buffers in order.
What I meant though was for GRO, we don't know how large the received
packet is going to be. Mergable rx buffers lets us allocate a pool of
data for all incoming packets instead of allocating max packet size *
max packets.
recvmmsg expects an array of msghdrs and I presume each needs to be
given a fixed size. So this seems incompatible with mergable rx
buffers.
Regards,
Anthony Liguori
>
>> >
>> > Stefan
2013 May 30
2
updated: kvm networking todo wiki
Stefan Hajnoczi <stefanha at gmail.com> writes:
> On Thu, May 30, 2013 at 7:23 AM, Rusty Russell <rusty at rustcorp.com.au> wrote:
>> Anthony Liguori <anthony at codemonkey.ws> writes:
>>> Rusty Russell <rusty at rustcorp.com.au> writes:
>>>> On Fri, May 24, 2013 at 08:47:58AM -0500, Anthony Liguori wrote:
>>>>> FWIW, I think
2013 May 30
2
updated: kvm networking todo wiki
Stefan Hajnoczi <stefanha at gmail.com> writes:
> On Thu, May 30, 2013 at 7:23 AM, Rusty Russell <rusty at rustcorp.com.au> wrote:
>> Anthony Liguori <anthony at codemonkey.ws> writes:
>>> Rusty Russell <rusty at rustcorp.com.au> writes:
>>>> On Fri, May 24, 2013 at 08:47:58AM -0500, Anthony Liguori wrote:
>>>>> FWIW, I think