From: Ian McDonald <imcdnzl@gmail.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
bunk@stusta.de, jengelh@linux01.gwdg.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PKT_SCHED]: Rework QoS and/or fair queueing configuration
Date: Wed, 2 Nov 2005 08:54:45 +1300 [thread overview]
Message-ID: <cbec11ac0511011154r13e7b695g@mail.gmail.com> (raw)
In-Reply-To: <20051101141302.GM23537@postel.suug.ch>
On 02/11/05, Thomas Graf <tgraf@suug.ch> wrote:
>
> Make "QoS and/or fair queueing" have its own menu, it's too big to be
> inlined into "Network options". Remove the obsolete NET_QOS option.
> Automatically select NET_CLS if needed. Do the same for NET_ESTIMATOR
> but allow it to be selected manually for statistical purposes. Add
> comments to separate queueing from classification. Fix dependencies
> and ordering of classifiers. Improve descriptions/help texts and
> remove outdated pieces.
>
Thomas I think the timing ones can be improved slightly out of the
discussion at here:
http://marc.theaimsgroup.com/?l=linux-netdev&m=112912015311659&w=2
I keep meaning to submit a patch but low on my todo list. Feel free to
do so if you wish or else I will get around to it one day. I know
Arnaldo has also mentioned ktimers for the future (which I haven't yet
read) which may help in this area as well.
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
next prev parent reply other threads:[~2005-11-01 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0510280902470.6910@yvahk01.tjqt.qr>
2005-10-31 10:26 ` [2.6 patch] fix the "QoS and/or fair queueing" menu Adrian Bunk
2005-10-31 13:27 ` Thomas Graf
2005-11-01 14:13 ` [PKT_SCHED]: Rework QoS and/or fair queueing configuration Thomas Graf
2005-11-01 19:54 ` Ian McDonald [this message]
2005-11-01 21:47 ` Patrick McHardy
2005-11-03 4:25 ` Arnaldo Carvalho de Melo
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=cbec11ac0511011154r13e7b695g@mail.gmail.com \
--to=imcdnzl@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=bunk@stusta.de \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).