From: Eric Dumazet <eric.dumazet@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Albert Cahalan <acahalan@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: txqueuelen has wrong units; should be time
Date: Sun, 27 Feb 2011 08:54:12 +0100 [thread overview]
Message-ID: <1298793252.8726.45.camel@edumazet-laptop> (raw)
In-Reply-To: <alpine.DEB.1.10.1102270758580.11974@uplift.swm.pp.se>
Le dimanche 27 février 2011 à 08:02 +0100, Mikael Abrahamsson a écrit :
> On Sun, 27 Feb 2011, Albert Cahalan wrote:
>
> > Nanoseconds seems fine; it's unlikely you'd ever want
> > more than 4.2 seconds (32-bit unsigned) of queue.
>
> I think this is shortsighted and I'm sure someone will come up with a case
> where 4.2 seconds isn't enough. Let's not build in those kinds of
> limitations from start.
>
> Why not make it 64bit and go to picoseconds from start?
>
> If you need to make it 32bit unsigned, I'd suggest to start from
> microseconds instead. It's less likely someone would want less than a
> microsecond of queue, than someone wanting more than 4.2 seconds of queue.
>
32 or 64 bits doesnt matter a lot. At Qdisc stage we have up to 40 bytes
available in skb->sb[] for our usage.
Problem is some machines have slow High Resolution timing services.
_If_ we have a time limit, it will probably use the low resolution (aka
jiffies), unless high resolution services are cheap.
I was thinking not having an absolute hard limit, but an EWMA based one.
next prev parent reply other threads:[~2011-02-27 7:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 5:44 txqueuelen has wrong units; should be time Albert Cahalan
2011-02-27 7:02 ` Mikael Abrahamsson
2011-02-27 7:54 ` Eric Dumazet [this message]
2011-02-27 8:27 ` Albert Cahalan
2011-02-27 10:55 ` Jussi Kivilinna
2011-02-27 20:07 ` Eric Dumazet
2011-02-27 21:32 ` Jussi Kivilinna
2011-02-28 11:43 ` Jussi Kivilinna
2011-02-28 13:10 ` Eric Dumazet
2011-02-28 18:31 ` Jussi Kivilinna
2011-02-28 16:11 ` John W. Linville
2011-02-28 16:48 ` Eric Dumazet
2011-02-28 16:55 ` John W. Linville
2011-02-28 17:18 ` Eric Dumazet
2011-02-28 21:45 ` John Heffner
2011-03-01 4:11 ` Albert Cahalan
2011-03-01 4:18 ` David Miller
2011-03-01 6:54 ` Albert Cahalan
2011-03-01 7:25 ` David Miller
2011-03-01 7:26 ` Eric Dumazet
2011-03-01 19:37 ` Albert Cahalan
2011-03-01 20:14 ` Eric Dumazet
2011-03-01 20:16 ` Eric Dumazet
2011-03-02 3:10 ` Mikael Abrahamsson
2011-03-02 20:25 ` Chris Friesen
2011-03-01 5:01 ` Eric Dumazet
2011-03-01 5:36 ` Eric Dumazet
2011-02-27 23:33 ` Albert Cahalan
2011-02-28 11:23 ` Jussi Kivilinna
2011-03-02 21:54 ` [RFC LOL OMG] pfifo_lat: qdisc that limits dequeueing based on estimated link latency John W. Linville
2011-03-02 22:08 ` John W. Linville
2011-03-03 12:51 ` Eric Dumazet
2011-02-28 15:38 ` txqueuelen has wrong units; should be time Hagen Paul Pfeifer
2011-02-28 16:37 ` Albert Cahalan
2011-02-28 17:45 ` John W. Linville
2011-02-28 17:20 ` Bill Sommerfeld
2011-02-28 21:51 ` John Heffner
2011-03-01 0:46 ` Mikael Abrahamsson
2011-03-02 6:25 ` Stephen Hemminger
2011-03-02 6:41 ` Mikael Abrahamsson
2011-03-02 7:07 ` Stephen Hemminger
2011-03-02 16:41 ` Mikael Abrahamsson
2011-03-02 16:50 ` Eric Dumazet
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=1298793252.8726.45.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=acahalan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swmike@swm.pp.se \
/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