netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: marcelo.leitner@gmail.com
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
	nhorman@tuxdriver.com, vyasevich@gmail.com
Subject: Re: [PATCH net] sctp: fix recovering from 0 win with small data chunks
Date: Fri, 23 Dec 2016 14:02:09 -0500 (EST)	[thread overview]
Message-ID: <20161223.140209.1226868882402302341.davem@davemloft.net> (raw)
In-Reply-To: <d9025eef1b2be8e7097fd4a5db73b4f5c0f5418b.1482510289.git.marcelo.leitner@gmail.com>

From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Date: Fri, 23 Dec 2016 14:29:37 -0200

> Currently if SCTP closes the receive window with window pressure, mostly
> caused by excessive skb overhead on payload/overheads ratio, SCTP will
> close the window abruptly while saving the delta on rwnd_press. It will
> start recovering rwnd as the chunks are consumed by the application and
> the rwnd_press will be only recovered after rwnd reach the same value as
> of rwnd_press, mostly to prevent silly window syndrome.
> 
> Thing is, this is very inefficient with small data chunks, as with those
> it will never reach back that value, and thus it will never recover from
> such pressure. This means that we will not issue window updates when
> recovering from 0 window and will rely on a sender retransmit to notice
> it.
> 
> The fix here is to remove such threshold, as no value is good enough: it
> depends on the (avg) chunk sizes being used.
> 
> Test with netperf -t SCTP_STREAM -- -m 1, and trigger 0 window by
> sending SIGSTOP to netserver, sleep 1.2, and SIGCONT.
> Rate limited to 845kbps, for visibility. Capture done at netserver side.
 ...
> Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>

Applied.

      reply	other threads:[~2016-12-23 19:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23 16:29 [PATCH net] sctp: fix recovering from 0 win with small data chunks Marcelo Ricardo Leitner
2016-12-23 19:02 ` 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=20161223.140209.1226868882402302341.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=vyasevich@gmail.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).