On Wed, Jun 28, 2017 at 9:17 AM, Sun Paul <paulrbk@xxxxxxxxx> wrote:
> hi Xin
>
> do you mean TX_QUEUE/RX_QUEUE in /proc/net/sctp/assocs instead of last
> two column?
>
> ASSOC SOCK STY SST ST HBKT ASSOC-ID TX_QUEUE RX_QUEUE UID INODE
> LPORT RPORT LADDRS <-> RADDRS HBINT INS OUTS MAXRT T1X T2X RTXC
ah, your kernel is too old. it's supported since (v3.9-rc5):
commit f406c8b9693f2f71ef2caeb0b68521a7d22d00f0
Author: Dilip Daya <dilip.daya@xxxxxx>
Date: Tue Apr 16 01:39:07 2013 +0000
sctp: Add buffer utilization fields to /proc/net/sctp/assocs
after which, # cat /proc/net/sctp/assocs
ASSOC SOCK STY SST ST HBKT ASSOC-ID TX_QUEUE RX_QUEUE UID INODE
LPORT RPORT LADDRS <-> RADDRS HBINT INS OUTS MAXRT T1X T2X RTXC wmema
wmemq sndbuf rcvbuf
then the last two column: "sndbuf" "rcvbuf"
>
> On Tue, Jun 27, 2017 at 7:41 PM, Xin Long <lucien.xin@xxxxxxxxx> wrote:
>> On Tue, Jun 27, 2017 at 3:56 PM, Sun Paul <paulrbk@xxxxxxxxx> wrote:
>>> Hi All
>>>
>>>
>>> what is the max value of TX_QUEUE and RX_QUEUE in /proc/net/sctp/assoc?
>> TX_QUEUE is assoc->sndbuf_used
>> RX_QUEUE is assoc->rmem_alloc
>>
>> when sendmsg and ep->sndbuf_policy is set, it does the check:
>> (asoc->sndbuf_used < sk->sk_sndbuf)
>>
>> when recvmsg and ep->rcvbuf_policy is set, it does the check:
>> (asoc->rmem_alloc < sk->sk_rcvbuf)
>>
>> so what you're asking is how to know the value of sk->sk_sndbuf/sk_rcvbuf.
>>
>> by /proc/net/sctp/assoc, it's the last two column: sndbuf rcvbuf
>> by "sctp_diag interface", it's mem[SK_MEMINFO_SNDBUF/SK_MEMINFO_RCVBUF]
>> by getsockopt, it's SO_SNDBUF/SO_RCVBUF
>>
>>
>>>
>>> How we can determine the value?
>>>
>>> - RBK
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
>>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
