From: Pavel Machek <pavel@ucw.cz>
To: Rick Jones <rick.jones2@hp.com>
Cc: Tianji Li <Tianji.Li@nuim.ie>, Dave T?ht <d@taht.net>,
sedat.dilek@gmail.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org,
bloat-devel@lists.bufferbloat.net, linux-kernel@vger.kernel.org
Subject: Re: ANNOUNCE: debloat-testing kernel git tree
Date: Sun, 13 Mar 2011 11:27:17 +0100 [thread overview]
Message-ID: <20110313102716.GC1827@ucw.cz> (raw)
In-Reply-To: <1299610096.2087.8.camel@tardy>
Hi!
> > Bandwidth varies greatly with time. On cellphone, you can go from
> > 5KB/sec GPRS to 300KB/sec HSDPA and back...
>
> How quickly/often and does that trigger an event in the host that would
> allow adjustment of the queue?
I'd expect it to get fast when you leave the building, and back to
slow when you re-enter. It all depends how good 3G coverage is, but
seeing it change more than once a minute is not that uncommon.
Event... not sure. Linux can ask for current signal strength, and I
assume connection type works in similar way...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2011-03-13 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 22:22 ANNOUNCE: debloat-testing kernel git tree John W. Linville
2011-02-27 15:23 ` Sedat Dilek
2011-02-27 15:23 ` Sedat Dilek
2011-02-27 15:31 ` Dave Täht
2011-02-27 15:31 ` Dave Täht
2011-02-27 15:38 ` Sedat Dilek
2011-02-27 15:56 ` Dave Täht
2011-02-27 16:01 ` Sedat Dilek
2011-02-27 16:01 ` Sedat Dilek
2011-02-27 16:25 ` Dave Täht
2011-02-27 16:25 ` Dave Täht
2011-03-03 18:16 ` Rick Jones
2011-03-03 18:19 ` John W. Linville
2011-03-03 19:45 ` Tianji Li
2011-03-03 19:45 ` Tianji Li
2011-03-03 22:33 ` Rick Jones
2011-03-08 6:58 ` Pavel Machek
2011-03-08 18:48 ` Rick Jones
2011-03-08 18:48 ` Rick Jones
2011-03-13 10:27 ` Pavel Machek [this message]
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=20110313102716.GC1827@ucw.cz \
--to=pavel@ucw.cz \
--cc=Tianji.Li@nuim.ie \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=d@taht.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=sedat.dilek@gmail.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.