All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrik Nordstrom <hno@marasystems.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages
Date: Sun, 09 Dec 2001 16:45:43 +0000	[thread overview]
Message-ID: <marc-lartc-100791644709315@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100785524509147@msgid-missing>

On Sunday 09 December 2001 16.01, jamal wrote:
> Henrik,
> Can you please try the attahed patch against iproute2-2.4.7-now-ss010824?

Seems to make the tc userspace program to properly reject the arguments.


It is a bit sad that one cannot queue packets in ingress. Would be quite 
useful to make ingress shaping behave more sane than what can be acheived 
with the queueless filter police mechanism.


netfilter supports queueing/delaying of packets and then resume processing 
them at a later time using nf_reinject, so I think it should be possible to 
implement a ingress queue without too much effort.. but then the netfilter 
queueing seems to be very simplistic only supporting one queue per protocol 
family and this queueing interface is already used for queueing packets to 
userspace, so perhaps not as easy as I thought..

Queueing in netfilter works by

1. The queueing mechanism registers it's handler by calling 
nf_register_queue_handler. Only one queue handler per protocol family is 
supported.

2. On packets needed to be queued, return NF_QUEUE

3. When the queue handler is done with the packet, it calls nf_reinject with 
a new verdict.

4. If the packet was not dropped/stolen, netfilter processing continues at 
the next hook (not priority).

The queue handler gets the following information: skb, protocol family, nf 
hook number, and in/out devices.

Regards
Henrik

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2001-12-09 16:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-08 20:43 [LARTC] Re: further CBQ/tc documentation ds9a.nl/lartc/manpages jamal
2001-12-08 21:30 ` bert hubert
2001-12-08 21:56 ` jamal
2001-12-08 23:08 ` bert hubert
2001-12-08 23:29 ` jamal
2001-12-08 23:30 ` jamal
2001-12-08 23:45 ` Henrik Nordstrom
2001-12-08 23:54 ` bert hubert
2001-12-09  1:19 ` jamal
2001-12-09  1:35 ` bert hubert
2001-12-09  2:11 ` jamal
2001-12-09  2:30 ` jamal
2001-12-09 11:38 ` Henrik Nordstrom
2001-12-09 14:40 ` bert hubert
2001-12-09 14:49 ` jamal
2001-12-09 15:01 ` jamal
2001-12-09 15:49 ` Henrik Nordstrom
2001-12-09 16:45 ` Henrik Nordstrom [this message]
2001-12-09 21:41 ` jamal
2001-12-09 22:33 ` Michael T. Babcock
2001-12-09 22:36 ` Michael T. Babcock
2001-12-10  1:12 ` Cédric Rivard
2001-12-10  7:53 ` Don Cohen
2001-12-10  8:38 ` Martin Devera
2001-12-10  8:41 ` Henrik Nordstrom
2001-12-10  9:59 ` Henrik Nordstrom
2001-12-10 11:35 ` Martin Devera
2001-12-10 11:59 ` Martin Devera
2001-12-10 12:00 ` Henrik Nordstrom
2001-12-10 12:14 ` bert hubert
2001-12-10 12:25 ` Henrik Nordstrom
2001-12-10 12:52 ` Martin Devera
2001-12-10 13:29 ` jamal
2001-12-10 13:40 ` Martin Devera
2001-12-10 13:42 ` Jim Fleming
2001-12-10 13:52 ` Michael T. Babcock
2001-12-10 13:54 ` Michael T. Babcock
2001-12-10 13:56 ` Gerry Creager N5JXS
2001-12-10 13:58 ` Michael T. Babcock
2001-12-10 14:02 ` Martin Devera
2001-12-10 14:51 ` Jim Fleming

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-100791644709315@msgid-missing \
    --to=hno@marasystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.