All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Hickey <bugfood-ml@fatooh.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to see the sfq hash table ?
Date: Thu, 23 Aug 2007 04:15:31 +0000	[thread overview]
Message-ID: <46CD09E3.9050403@fatooh.org> (raw)
In-Reply-To: <46C45125.4030602@boreham.org>

Andy Furniss wrote:
> David Boreham wrote:
>> I'm grappling with a problem that looks like sfq is not working
>> (packets don't get fairly queued, they appear to be always
>> sent FIFO). My configuration appears to be correct.
>> The machine is running quite an old kernel and if I could
>> convince myself that the sfq code it has is just broken, I'd
>> spend the time to upgrade it. Is there any way to inspect or
>> dump the sfq hash table on a running machine ?
> 
> I don't think so

I don't know of any way either, though I will probably write one 
eventually for diagnostic use.

> - I would use tcpdump, if you use perturb don't set it 
> too low as it causes packet reordering.

A couple other notes:

1. SFQ won't do much unless it's attached to a rate limiting qdisc such 
as HTB, with a specified rate less than that of your Internet connection.

2. SFQ doesn't currently handle more than 128 concurrent flows (TCP 
connections, etc.), and I would expect the fairness to degrade sooner 
than that. I have been working on patches to address this, among other 
things.

> There is currently work going on to merge sfq/esfq and the hash will be 
> jhash so should be better than the current one.

My own role in that is taking forever, but I am indeed still working on 
it...

-Corey
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2007-08-23  4:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16 13:29 [LARTC] How to see the sfq hash table ? David Boreham
2007-08-22 23:24 ` Andy Furniss
2007-08-23  4:15 ` Corey Hickey [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=46CD09E3.9050403@fatooh.org \
    --to=bugfood-ml@fatooh.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.