From: jamal <hadi@cyberus.ca>
To: lartc@vger.kernel.org
Subject: Re: [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21
Date: Fri, 12 Jul 2002 09:57:13 +0000 [thread overview]
Message-ID: <marc-lartc-102646827621987@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102638963713023@msgid-missing>
On Fri, 12 Jul 2002, Andrei Boros wrote:
>
> Couldn't try the same thing under 2.4 because I have no machine with 2.4
> at my disposal.
>
fair enough.
BTW, now that i am actually thinking, another very stupid question -- if you
are trying to ingress police, do you have policing compiled in under QoS?
double check this. Infact the more i think about the more i believe this
may be your problem.
> How do I turn on debugging in the ingress code?
>
If you edit net/sched/sch_ingress.c at the very top you should see:
----------
#undef DEBUG_INGRESS
#ifdef DEBUG_INGRESS /* control */
#define DPRINTK(format,args...) printk(KERN_DEBUG format,##args)
#else
#define DPRINTK(format,args...)
#endif
#if 0 /* data */
#define D2PRINTK(format,args...) printk(KERN_DEBUG format,##args)
#else
#define D2PRINTK(format,args...)
#endif
-----------
convert to:
---
#if 1
#define DPRINTK(format,args...) printk(KERN_DEBUG format,##args)
#else
#define DPRINTK(format,args...)
#endif
#if 1 /* data */
#define D2PRINTK(format,args...) printk(KERN_DEBUG format,##args)
#else
#define D2PRINTK(format,args...)
#endif
-----------
run your tests and look at dmesg.
cheers,
jamal
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-12 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 12:06 [Linux Diffserv] Re: [LARTC] ingress qdisc on kernel 2.2.21 with jamal
2002-07-12 9:57 ` jamal [this message]
2002-07-12 10:11 ` jamal
2002-07-12 10:49 ` Julian Anastasov
2002-07-12 11:37 ` jamal
2002-07-12 12:26 ` Julian Anastasov
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-102646827621987@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 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.