From: Martijn van Oosterhout <kleptog@cupid.suninternet.com>
To: linux kernel <linux-kernel@vger.rutgers.edu>
Subject: [RFC] Packet-Shaping-HOWTO
Date: Sun, 26 Mar 2000 02:28:12 +1100 [thread overview]
Message-ID: <38DCDB0C.1E52E915@cupid.suninternet.com> (raw)
Hello people,
Recently I've had occasion to try to make the QoS and queueing
code from the 2.2 kernel to work for me, but found the
documentation to be a bit technical and not really aimed for
users. So, I've summed up my experience with the packet
shaping and stuffed it all into a HOWTO.
However some of it is still guess work since there are some
concepts going on here that I still don't get. No matter,
I would just like people to read over it to see if I got
it right.
Note that this is specifically 2.2, I don't know if
2.[34] is the same.
http://cupid.suninternet.com/~kleptog/Packet-Shaping-HOWTO.html
Please CC any replies.
--
Martijn van Oosterhout <kleptog@cupid.suninternet.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-03-25 15:23 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=38DCDB0C.1E52E915@cupid.suninternet.com \
--to=kleptog@cupid.suninternet.com \
--cc=linux-kernel@vger.rutgers.edu \
/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