All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Michael Tuexen <michael.tuexen@lurchi.franken.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	Xin Long <lucien.xin@gmail.com>,
	network dev <netdev@vger.kernel.org>,
	linux-sctp@vger.kernel.org, David Miller <davem@davemloft.net>,
	David Ahern <dsa@cumulusnetworks.com>,
	Eric Dumazet <edumazet@google.com>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: [PATCH net] sctp: not allow to set rto_min with a value below 200 msecs
Date: Mon, 28 May 2018 15:56:40 -0300	[thread overview]
Message-ID: <20180528185640.GA3788@localhost.localdomain> (raw)
In-Reply-To: <D8455431-D0D7-4420-BEBF-E0B5BE5DBC97@lurchi.franken.de>

On Sun, May 27, 2018 at 10:58:35AM +0200, Michael Tuexen wrote:
...
> >>> Patch looks fine, you probably want to note this hard minimum in man(7) sctp as
> >>> well
> >>> 
> >> I'm aware of some signalling networks which use RTO.min of smaller values than 200ms.
> >> So could this be reduced?
> > 
> > Hi Michael,
> > 
> > What value do they use?
> I have seen values of
> RTO.Min     =  50ms
> RTO.Max     = 200ms
> RTO.Initial = 100ms

Those look doable to me.

Thanks,
Marcelo

WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Michael Tuexen <michael.tuexen@lurchi.franken.de>
Cc: Dmitry Vyukov <dvyukov@google.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	Xin Long <lucien.xin@gmail.com>,
	network dev <netdev@vger.kernel.org>,
	linux-sctp@vger.kernel.org, David Miller <davem@davemloft.net>,
	David Ahern <dsa@cumulusnetworks.com>,
	Eric Dumazet <edumazet@google.com>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: [PATCH net] sctp: not allow to set rto_min with a value below 200 msecs
Date: Mon, 28 May 2018 18:56:40 +0000	[thread overview]
Message-ID: <20180528185640.GA3788@localhost.localdomain> (raw)
In-Reply-To: <D8455431-D0D7-4420-BEBF-E0B5BE5DBC97@lurchi.franken.de>

On Sun, May 27, 2018 at 10:58:35AM +0200, Michael Tuexen wrote:
...
> >>> Patch looks fine, you probably want to note this hard minimum in man(7) sctp as
> >>> well
> >>> 
> >> I'm aware of some signalling networks which use RTO.min of smaller values than 200ms.
> >> So could this be reduced?
> > 
> > Hi Michael,
> > 
> > What value do they use?
> I have seen values of
> RTO.Min     =  50ms
> RTO.Max     = 200ms
> RTO.Initial = 100ms

Those look doable to me.

Thanks,
Marcelo

  reply	other threads:[~2018-05-28 18:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 17:41 [PATCH net] sctp: not allow to set rto_min with a value below 200 msecs Xin Long
2018-05-25 17:41 ` Xin Long
2018-05-25 19:13 ` Neil Horman
2018-05-25 19:13   ` Neil Horman
2018-05-26 15:42   ` Michael Tuexen
2018-05-26 15:42     ` Michael Tuexen
2018-05-26 15:50     ` Dmitry Vyukov
2018-05-26 15:50       ` Dmitry Vyukov
2018-05-27  1:01       ` Neil Horman
2018-05-27  1:01         ` Neil Horman
2018-05-28 19:43         ` Marcelo Ricardo Leitner
2018-05-28 19:43           ` Marcelo Ricardo Leitner
2018-05-29 11:41           ` Neil Horman
2018-05-29 11:41             ` Neil Horman
2018-05-29 13:06             ` Michael Tuexen
2018-05-29 13:06               ` Michael Tuexen
2018-05-29 15:45               ` Marcelo Ricardo Leitner
2018-05-29 15:45                 ` Marcelo Ricardo Leitner
2018-05-29 16:03                 ` Neal Cardwell
2018-05-29 16:03                   ` Neal Cardwell
2018-05-29 17:06                   ` Marcelo Ricardo Leitner
2018-05-29 17:06                     ` Marcelo Ricardo Leitner
2018-05-29 17:45                     ` Xin Long
2018-05-29 17:45                       ` Xin Long
2018-05-29 18:02                       ` Marcelo Ricardo Leitner
2018-05-29 18:02                         ` Marcelo Ricardo Leitner
2018-06-04  8:34                       ` Dmitry Vyukov
2018-06-04  8:34                         ` Dmitry Vyukov
2018-06-04 12:15                         ` Xin Long
2018-06-04 12:15                           ` Xin Long
2018-05-27  8:58       ` Michael Tuexen
2018-05-27  8:58         ` Michael Tuexen
2018-05-28 18:56         ` Marcelo Ricardo Leitner [this message]
2018-05-28 18:56           ` Marcelo Ricardo Leitner

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=20180528185640.GA3788@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsa@cumulusnetworks.com \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=michael.tuexen@lurchi.franken.de \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=syzkaller@googlegroups.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 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.