> -----Original Message-----
> From: [email protected] <[email protected]>
> On Behalf Of David Miller
> Sent: 19-Apr-19 17:41
> To: Tung Quang Nguyen <[email protected]>
> Cc: [email protected]; [email protected]
> Subject: Re: [tipc-discussion][net-next v1] tipc: introduce new socket option
> TIPC_SOCK_RECVQ_USED
>
> From: Tung Nguyen <[email protected]>
> Date: Thu, 18 Apr 2019 21:02:19 +0700
>
> > When using TIPC_SOCK_RECVQ_DEPTH for getsockopt(), it returns the
> > number of buffers in receive socket buffer which is not so helpful for
> > user space applications.
> >
> > This commit introduces the new option TIPC_SOCK_RECVQ_USED which
> > returns the current allocated bytes of the receive socket buffer.
> > This helps user space applications dimension its buffer usage to avoid
> > buffer overload issue.
> >
> > Signed-off-by: Tung Nguyen <[email protected]>
>
> TIPC folks, please review.
Acked-by: Jon Maloy <[email protected]>
It would of course be nicer if we could recycle TIPC_SOCK_RECV_QUEUE_DEPTH for
this purpose, but that would mean altering the current ABI and incur a
(probably very low) risk of breaking existing application.
I am not particularly happy with this, but do we have users who claim it would
be useful for them.
///jon
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion
