From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Ricardo Leitner 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 Message-ID: <20180528185640.GA3788@localhost.localdomain> References: <20180525191319.GB392@hmswarspite.think-freely.org> <71FD541D-25FE-4100-980B-C3A0CEAF6CD4@lurchi.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dmitry Vyukov , Neil Horman , Xin Long , network dev , linux-sctp@vger.kernel.org, David Miller , David Ahern , Eric Dumazet , syzkaller To: Michael Tuexen Return-path: Received: from mail-qt0-f195.google.com ([209.85.216.195]:42127 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755637AbeE1S4p (ORCPT ); Mon, 28 May 2018 14:56:45 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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