On Wed, 12 Sep 2007 13:28:42 -0700
Rick Jones [EMAIL PROTECTED] wrote:
The api in netlink should be in milliseconds rather than compensating
in the application (iproute2).
My understanding of the in-kernel rtnetlink code is far from complete,
but it doesn't seem to have much in the
Your observations are correct. rtnetlink can't/shouldn't be doing conversions
itself. The 'ip' command should use a consistent unit for all values and
do conversions if necessary.
That being the case I'll start looking to see what is involved in
leveraging the time conversion stuff in tc for
The api in netlink should be in milliseconds rather than compensating
in the application (iproute2).
My understanding of the in-kernel rtnetlink code is far from complete,
but it doesn't seem to have much in the way of provisions for unit
conversion, which would suggest no nice suffix-based
Stephen Hemminger wrote:
On Tue, 4 Sep 2007 13:20:47 -0700 (PDT)
Rick Jones [EMAIL PROTECTED] 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
On Tue, 4 Sep 2007 13:20:47 -0700 (PDT)
Rick Jones [EMAIL PROTECTED] 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
Stephen Hemminger wrote:
On Tue, 4 Sep 2007 13:20:47 -0700 (PDT)
Rick Jones [EMAIL PROTECTED] 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
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
