All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Could anyone explain the slot and bucket concept in SFQ
Date: Thu, 13 Jan 2005 10:09:16 +0000	[thread overview]
Message-ID: <41E648CC.8020107@dsl.pipex.com> (raw)
In-Reply-To: <200501101527.j0AFRG77008922@mx4.ust.hk>

Wang Feng wrote:
> Dear all,
> 
> I'm reading codes in sch_sqf.c in kernel 2.4 of Linux.
> I find I messed up with the concept of slot, bucket and hash tables.

I get messed up too when I read it. You can play with the values if you 
use ESFQ.

I can't explain in detail but at high level -

Slot is linked list of packets whose IPs + src port (if TCP/UDP) hash 
into same hash bin/bucket. Slots get dequed in turn using DRR.

Hash buckets/bins (1024 of by default) is the what hash function maps 
to, to try and seperate flows. You can make it bigger with esfq so 
hopefully get less chance of different flows mapping to same bin and so 
their packets ending up being queued in same slot.

  Could
> anyone explain the data stucture of the hash tables a little to me.
> 
> Thanks very much.
> 
> Best,
> Franklin
> 
> BTW: I can not understand why the number of entries of dep[SFQ_DEPTH*]
> should be twice:(

Don't know but esfq defines pointer rather than array here.

Andy.


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

      reply	other threads:[~2005-01-13 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 15:27 [LARTC] Could anyone explain the slot and bucket concept in SFQ to me? Wang Feng
2005-01-13 10:09 ` Andy Furniss [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=41E648CC.8020107@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --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.