netdev - Re: [PATCH] [RFC] allow admin/users to specify rto_min in milliseconds rather than jiffies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 05 Sep 2007 10:11:12 -0700
From:	Rick Jones <rick.jones2@...com>
To:	Stephen Hemminger <shemminger@...ux-foundation.org>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] [RFC] allow admin/users to specify rto_min in	milliseconds
 rather than jiffies

Stephen Hemminger wrote:
> On Tue, 4 Sep 2007 13:20:47 -0700 (PDT)
> Rick Jones <rick.jones2@...com> wrote:
> 
> 
>>Build upon David Miller's initial patches to set the per-route rto_min
>>so users can specify the rto_min in the same units (milliseconds) in
>>which they are displayed.  This is desirable because asking users to
>>convert to and from jiffies themselves, when there can be different
>>values of HZ from system to system would be error prone.
>>
>>Signed-off-by: Rick Jones <rick.jones2@...com>
>>---
> 
> 
> The api in netlink should be in milliseconds rather than compensating
> in the application (iproute2).

In unrelated work I found myself using tc to setup some WAN emulation. 
There I noticed that one can specify times using a units suffix. So, one 
can say 100ms, 100us, or 100s.

That seems like a nice, friendly interface.  I've not looked yet to see 
if it was converting up in tc and then passing a consistent unit to the 
kernel, or if all the conversion was happening in the kernel.

rick jones
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html