All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
Date: Thu, 03 Jul 2003 12:06:23 +0000	[thread overview]
Message-ID: <marc-lartc-105723443911141@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105593587226514@msgid-missing>

On Thursday 03 July 2003 13:14, lartc@go.ro wrote:
> yes I think it depends on traffic...
> but why this?
> PS
> 1) http://qos.dyndns.org:3389/cgi-bin/fom?file@ what should I use on my
> K6 ??? default it's PSCHED_JIFFIES, i think!!
I'm not sure but if you do cat /proc/cpuinfo, do you seetsc in the flags?  I 
think that means your cpu has a timestamp counter.

> 2) http://qos.dyndns.org:3389/cgi-bin/fom?fileV those filter destroy
> patches are applyed in 2.4.21 ??
Yes.

> 3) http://qos.dyndns.org:3389/cgi-bin/fom?file! What SFQ latency should I
> use?
>             SFQ qdisc has a default queue length of 128 packets!!!!
Try the default sfq and see if that's enough.  If not, you can try to change 
the queue depth.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-07-03 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 11:29 [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen) David Watson
2003-06-18 16:43 ` Stef Coene
2003-06-18 18:53 ` Giannis Stoilis
2003-06-18 19:10 ` Stef Coene
2003-06-18 19:17 ` Giannis Stoilis
2003-06-18 19:55 ` Stef Coene
2003-06-20 15:20 ` David Watson
2003-06-20 19:41 ` Giannis Stoilis
2003-07-03 12:06 ` Stef Coene [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=marc-lartc-105723443911141@msgid-missing \
    --to=stef.coene@docum.org \
    --cc=lartc@vger.kernel.org \
    /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.