From: David Miller <davem@davemloft.net>
To: dilip.daya@hp.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
nhorman@tuxdriver.com, dborkman@redhat.com
Subject: Re: [PATCH v4] sctp: Add buffer utilization fields to /proc/net/sctp/assocs
Date: Tue, 16 Apr 2013 16:40:19 -0400 (EDT) [thread overview]
Message-ID: <20130416.164019.1074985550251974378.davem@davemloft.net> (raw)
In-Reply-To: <1366112347.7478.10.camel@pro6455b.example.com>
From: Dilip Daya <dilip.daya@hp.com>
Date: Tue, 16 Apr 2013 07:39:07 -0400
> From: Dilip Daya <dilip.daya@hp.com>
>
> sctp: Add buffer utilization fields to /proc/net/sctp/assocs
>
> This patch adds the following fields to /proc/net/sctp/assocs output:
>
> - sk->sk_wmem_alloc as "wmema" (transmit queue bytes committed)
> - sk->sk_wmem_queued as "wmemq" (persistent queue size)
> - sk->sk_sndbuf as "sndbuf" (size of send buffer in bytes)
> - sk->sk_rcvbuf as "rcvbuf" (size of receive buffer in bytes)
>
> When small DATA chunks containing 136 bytes data are sent the TX_QUEUE
> (assoc->sndbuf_used) reaches a maximum of 40.9% of sk_sndbuf value when
> peer.rwnd = 0. This was diagnosed from sk_wmem_alloc value reaching maximum
> value of sk_sndbuf.
>
> TX_QUEUE (assoc->sndbuf_used), sk_wmem_alloc and sk_wmem_queued values are
> incremented in sctp_set_owner_w() for outgoing data chunks. Having access to
> the above values in /proc/net/sctp/assocs will provide a better understanding
> of SCTP buffer management.
...
> Signed-off-by: Dilip Daya <dilip.daya@hp.com>
> Acked-by: Neil Horman <nhorman@tuxdriver.com>
Applied.
prev parent reply other threads:[~2013-04-16 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 11:39 [PATCH v4] sctp: Add buffer utilization fields to /proc/net/sctp/assocs Dilip Daya
2013-04-16 20:40 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130416.164019.1074985550251974378.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=dilip.daya@hp.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).