Displaying 2 results from an estimated 2 matches for "recv_dgram".
2012 Dec 24
0
No subject
...gt;>> + /* For DGRAMs. */
>>> + struct vmci_handle dg_handle;
>>
>> Yep, should be a pointer where transports can hook in their private
>> data.
>
> I'm fixing this.
Yes, please, that is needed too to get started with virtio support.
>> Where is recv_dgram?
>
> The transport just enqueues sk_buffs in the socket's buffer, so the
> core socket code can just pull them off. So there's no explicit
> recv_dgram.
Ok.
>> Also why bind_dgram? I guess binding stream sockets doesn't make
>> sense for the vsock family?
&g...
2012 Dec 24
0
No subject
...gt;>> + /* For DGRAMs. */
>>> + struct vmci_handle dg_handle;
>>
>> Yep, should be a pointer where transports can hook in their private
>> data.
>
> I'm fixing this.
Yes, please, that is needed too to get started with virtio support.
>> Where is recv_dgram?
>
> The transport just enqueues sk_buffs in the socket's buffer, so the
> core socket code can just pull them off. So there's no explicit
> recv_dgram.
Ok.
>> Also why bind_dgram? I guess binding stream sockets doesn't make
>> sense for the vsock family?
&g...