From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: receiver window questions
Date: Fri, 30 May 2008 17:10:55 +0000 [thread overview]
Message-ID: <4840351F.1000908@hp.com> (raw)
In-Reply-To: <483EC663.1070805@hp.com>
Michael Tuexen wrote:
> Hi Vlad,
>
> is there any description available how the auto-tuning works?
There is no formal writeup. In short it works the same as TCP.
Essentially, we start out with a set buffer space and calculated
rwnd. Then as buffer space and window is consumed, we see if
buffer space is consumed faster then rwnd. If we reach a point
where default buffer space is consumed, but rwnd is not, we
grow the buffer space slowly up to the next threshold, thus allowing
all of rwnd to be consumed.
There is also a system-wide threshold that we look at when growing
the buffer. So that if the system is experiencing memory pressure
conditions, the growth and allocations will fail.
> But even with auto-tuning you still have the a_rwnd you report
> to the outside world (in SACKs) and an internal value which
> you use for tracking you buffer, right?
Buffer space tracking is separate from rwnd and a_rwnd that we
advertise.
-vlad
>
> Best regards
> Michael
>
next prev parent reply other threads:[~2008-05-30 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 15:06 receiver window questions Vlad Yasevich
2008-05-29 15:18 ` Michael Tuexen
2008-05-29 15:25 ` Neil Horman
2008-05-29 15:34 ` Michael Tuexen
2008-05-29 15:50 ` Vlad Yasevich
2008-05-29 16:12 ` Michael Tuexen
2008-05-29 23:51 ` Neil Horman
2008-05-30 7:50 ` Michael Tuexen
2008-05-30 13:02 ` Vlad Yasevich
2008-05-30 15:08 ` Michael Tuexen
2008-05-30 17:10 ` Vlad Yasevich [this message]
2008-05-30 20:23 ` Neil Horman
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=4840351F.1000908@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=linux-sctp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.