From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] esfq ? or wrr ?
Date: Sat, 15 Oct 2005 15:40:53 +0000 [thread overview]
Message-ID: <43512305.6E60C5FC@iswest.com> (raw)
In-Reply-To: <NHBBLNDNFKDMKNNKGOMMCEGFMMAA.gregoriandres@yahoo.com.ar>
Corey Hickey wrote:
>
> I still maintain ESFQ; the latest version is at:
> http://fatooh.org/esfq-2.6/
>
> This would be an appropriate time to ask:
> Does anybody have any fixes for or improvements to ESFQ that I don't
> know about? My patch doesn't have anything revolutionary -- I've been
> merely keeping Alexander Clouter's 2.6 port in sync with the upstream
> changes to SFQ.
>
> -Corey
1) I'd like for your code to support kernel version 2.4! It is crazy
that there are two branches of ESFQ.
2) ESFQ should be able to match a firewall mark, dport and sport. All
except CLASSIC should understand NOT ("! sport 22").
3) The documentation should be improved.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-10-15 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 1:26 [LARTC] esfq ? or wrr ? LinuXKiD
2005-10-15 6:15 ` Jonathan Day
2005-10-15 7:06 ` Corey Hickey
2005-10-15 11:50 ` LinuXKiD
2005-10-15 15:40 ` gypsy [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=43512305.6E60C5FC@iswest.com \
--to=gypsy@iswest.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox