From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] What is drop in Qdisc_ops for?
Date: Thu, 07 Aug 2003 12:25:08 +0000 [thread overview]
Message-ID: <marc-lartc-106025920704504@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106025213630464@msgid-missing>
Chris,
Have you discovered the following source of documentation on the QoS
APIs for linux, yet?
http://qos.ittc.ukans.edu/howto/index.html
: What is the operation drop() in Qdisc_ops for?
Well, from the userland perspective, drop is just like a netfilter -j
DROP. Essentially we are saying "throw that packet away".
: What are the requirements on a new qdisc?
/me retreats to userland, maybe the link above will provide an answer.
: As far as I can tell, the classfull qdiscs just pass it on to child
: qdiscs and classless qdiscs drop the most recently queued packet. I
: can't find any code that initiates all this though.
Again, try the above documentation.
: The operation is not described in the comments in sch_api.c where
: enqueue, dequeue, requeue, reset, init, destroy & change are described
: (dump isn't described either).
Here's a little bit on dump.
http://qos.ittc.ukans.edu/howto/node16.html
Good luck,
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-08-07 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 10:31 [LARTC] What is drop in Qdisc_ops for? Chris Paulson-Ellis
2003-08-07 12:25 ` Martin A. Brown [this message]
2003-08-07 13:07 ` Chris Paulson-Ellis
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-106025920704504@msgid-missing \
--to=mabrown-lartc@securepipe.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