netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Michal Soltys <soltys@ziu.info>
Cc: linux-net@vger.kernel.org, Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: Question about HFSC atm+man patches
Date: Sun, 23 Nov 2008 15:05:35 +0100	[thread overview]
Message-ID: <4929632F.3050200@trash.net> (raw)
In-Reply-To: <49292F54.4020803@ziu.info>

Michal Soltys wrote:
> I'm thinking about writing few simple patches that would introduce layer
> 2 adaptation to HFSC. Generally - instead of preparing adjusted rate
> table like some of the other qdiscs do (tbf, htb, ...), hfsc could
> simply adjust packets' lengths in qdisc code (and there are just few 
> places where it's done) - as it's used for all time / curve related 
> computations later. So the whole thing should be, at least in theory, 
> pretty straightforward.
> 
> The tc's interface would of course remain the same - that is - linklayer
> and overhead options, consistently with other qdiscs.
> 
> Would such approach be valid and possibly accepted ?

We already support generic size adjustment for all qdiscs. I'm
not sure about the userspace interface though.

> Another thing I'd like to add is detailed tc-hfsc man page (and maybe
> add/update other ones - but that's for a bit later).

That would be great.

       reply	other threads:[~2008-11-23 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49292F54.4020803@ziu.info>
2008-11-23 14:05 ` Patrick McHardy [this message]
2008-11-24 13:56   ` Question about HFSC atm+man patches Michal Soltys
2008-11-24 14:11     ` Patrick McHardy
2008-11-24 23:21       ` Michal Soltys
2008-11-26 22:54       ` Michal Soltys
2008-11-27 10:48         ` Patrick McHardy
2008-11-27 23:17           ` Michal Soltys
2008-12-04 13:55             ` Question - size tables implementation Michal Soltys

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=4929632F.3050200@trash.net \
    --to=kaber@trash.net \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=soltys@ziu.info \
    /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).