From: "Irénée BROCHIER" <irenee.brochier@etictelecom.com>
To: bridge@lists.osdl.org
Subject: [Bridge] brctl masking interrupts ?
Date: Mon, 18 Jul 2005 09:51:10 +0200 [thread overview]
Message-ID: <006101c58b6d$76cf7250$2f00a8c0@coco> (raw)
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
Hi all,
I recently discovered that when I am using brctl in my product, I got some troubles with a driver which need to quickly handle interrupts. Brct seems to "mask interrupts" for long time - more than 6 ms - when there is ethernet traffic in it.
I also noticed that there is a lot of messages on the console when there is trafic in the bridge.Here a sample of messages :
...
PROTO=17 192.168.0.43:137 192.168.0.255:137 L=78 S=0x00 I=387 F=0x0000 T=128
nf_hook: hook 1 already set.
skb: pf=2 (unowned) dev=br0 len=78
PROTO=17 192.168.0.43:137 192.168.0.255:137 L=78 S=0x00 I=387 F=0x0000 T=128
...
Maybe these two things are linked ?
These messages are quite boring but this is not my real problem. My problem is the enormous interrupt latency that brctl bring in my product.
My product runs with a linux 2.4.27 for arm.
Is what happens in my product normal ?
Is there any magical patch for my problem ?
Thanks all,
bye.
Irénée B.
[-- Attachment #2: Type: text/html, Size: 2394 bytes --]
reply other threads:[~2005-07-18 7:51 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='006101c58b6d$76cf7250$2f00a8c0@coco' \
--to=irenee.brochier@etictelecom.com \
--cc=bridge@lists.osdl.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.