netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Day <imipak@yahoo.com>
To: netdev@oss.sgi.com
Subject: Questions wrt QoS code on Linux
Date: Wed, 11 May 2005 21:40:39 -0700 (PDT)	[thread overview]
Message-ID: <20050512044040.61360.qmail@web31504.mail.mud.yahoo.com> (raw)

Hi,

Wondering if someone can answer a few questions on the
QoS code in Linux.

First off, I notice that all the code is lumped
together and much of it is generically labelled
"scheduling". I'm wondering if it might not be more
readable if the list were divided into four sections -
"queueing disciplines", "scheduling", "packet
classification" and "everything else". Would that seem
sensible? Or would it risk making things
over-structured?

Secondly, there seem to be an awful lot of QoS methods
not represented in Linux. Implementing them all might
easily double the kernel size for not very much
benefit, even if anyone could find the time to do so.
On the other hand, there are probably some that are
under development and others high on the wishlist.
Does anyone know what projects are currently underway
or being planned?

Jonathan


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail

             reply	other threads:[~2005-05-12  4:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-12  4:40 Jonathan Day [this message]
2005-05-12 12:20 ` Questions wrt QoS code on Linux Thomas Graf
  -- strict thread matches above, loose matches on Subject: below --
2005-05-12 19:07 Jonathan Day
2005-05-12 23:32 ` Thomas Graf

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=20050512044040.61360.qmail@web31504.mail.mud.yahoo.com \
    --to=imipak@yahoo.com \
    --cc=netdev@oss.sgi.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 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).