From: David Lang <david@lang.hm>
To: sahil grover <sahilgrover013@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] sfqCodel
Date: Fri, 10 Apr 2015 17:31:52 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1504101730210.13751@nftneq.ynat.uz> (raw)
In-Reply-To: <CADnS-2iXotj3BeQKxFtcjKB5z5VvU_Rqf7FBeU6WgnfXyMCU_Q@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 714 bytes --]
On Sat, 11 Apr 2015, sahil grover wrote:
> Hi
>
> i am very curious to know about sfqCodel.
>
> i guess i need to learn sfq first.
>
> So i tried with this "
> http://www.rdrop.com/users/paulmck/scalability/paper/sfq.2002.06.04.pdf"
> paper.
>
> But its so long and does not work for me.
>
> and i just want to know the concept of SFQ in simple words.
>
> So anyone please explain me about SFQ/sfqCoDel.
>
> Please tell me something.
First off, the paper you are looking at is 12 years old, so it predates all the
bufferbloat work. What we discovered is not in sfq
what we found is that the generic 'right' thing to use is fq_codel, not
sfq_codel. So why are you interested in that specifically?
David Lang
[-- Attachment #2: Type: TEXT/PLAIN, Size: 140 bytes --]
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2015-04-11 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 20:32 sahil grover
2015-04-11 0:31 ` David Lang [this message]
2015-04-11 7:57 ` sahil grover
2015-04-11 17:00 ` Dave Taht
2015-04-12 3:51 ` Mikael Abrahamsson
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1504101730210.13751@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=sahilgrover013@gmail.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