From: jamal <hadi@cyberus.ca>
To: lartc@vger.kernel.org
Subject: [LARTC] ANNOUNCE: tc filter extensions
Date: Sat, 04 Jan 2003 18:03:58 +0000 [thread overview]
Message-ID: <marc-lartc-104177871301094@msgid-missing> (raw)
I guess holidays means idle time which means idle minds which leads to
thumb twiddling which then leads to some work (which is sometimes useful)
Ive updated the traffic control patches i posted about six months ago.
Note, the current release does not break anything in tc. It is fully
backward compatible so you can choose not to use it and things will work
as they do today. Of course, it is very useful so you cant choose to
ignore it!
It's now upgraded to better than "use at your own risk" category.
tested on both uni and SMP 2.4.18 and 2.4.20.
http://www.cyberus.ca/~hadi/patches/action/
Bug reports and feedback are appreaciated.
A lot more goodies coming up, so this is just the tip. First steps are to
prove sanity of the idea.
cheers,
jamal
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-01-04 18:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-104177871301094@msgid-missing \
--to=hadi@cyberus.ca \
--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