From: Andreani Luca <landreani@seltatel.it>
To: lartc@vger.kernel.org
Subject: [LARTC] u32 classifier
Date: Mon, 14 Jul 2003 12:11:55 +0000 [thread overview]
Message-ID: <marc-lartc-105818475719019@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Dear list,
I have some problems with u32 classifier. I use a board based on Motorola
MPC8245 processor (ppc based). I noticed that when the u32_classify function
(in /net/sched/cls_u32.c) is called, it returns an error. Making some
printk-based debug I found that the critical point in the code is the
following:
#if !defined(__i386__) && !defined(__mc68000__)
if ((unsigned long)ptr & 3)
return -1;
#endif
The problem is that when I have a packet to be forwarded the classification
fails at this point (return -1, default class). This is not the case when
the packet is generated locally. The question is: what is the meaning of
this code, what happens if this check is removed in architectures other then
i386 and mc68000?
Thank's in advance,
Luca Andreani.
[-- Attachment #2: Type: text/html, Size: 1568 bytes --]
next reply other threads:[~2003-07-14 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 12:11 Andreani Luca [this message]
2007-06-02 9:19 ` [LARTC] u32 classifier terraja-based
2007-06-02 10:31 ` Afshin Tajvidi
2007-06-02 11:46 ` VladSun
2007-06-06 13:19 ` Catalin Bucur
2007-06-06 13:50 ` VladSun
2007-06-06 14:00 ` Catalin Bucur
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-105818475719019@msgid-missing \
--to=landreani@seltatel.it \
--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