From: "Nishit Shah" <nishit@elitecore.com>
To: <netfilter-devel@vger.kernel.org>
Cc: "'Patrick McHardy'" <kaber@trash.net>
Subject: Accessing conntrack memory on multicore machine
Date: Fri, 29 Feb 2008 16:12:47 +0530 [thread overview]
Message-ID: <005001c87abf$d328d570$797a8050$@com> (raw)
Hi,
I have following setup.
[root@manage scripts]# cat /proc/interrupts
CPU0 CPU1
0: 228177 547 IO-APIC-edge
timer
2: 0 0 XT-PIC
cascade
4: 446 0
IO-APIC-edge serial
8: 1 1 IO-APIC-edge
rtc
16: 137 0 IO-APIC-level
eth0, eth10, eth12, eth6, eth8
17: 1710 0 IO-APIC-level
eth1, eth11, eth13, eth2, eth7, eth9
18: 54 1 IO-APIC-level
eth3, eth4
19: 7454 0 IO-APIC-level
libata, eth5
NMI: 0 0
LOC: 228829 229844
ERR: 0
MIS: 0
I want to bind interrupts on eth0 to CPU0 and eth1 to CPU1
echo 1 > /proc/irq/16/smp_affinity
echo 2 > /proc/irq/17/smp_affinity
Now,
I am using CONNMARK target to do mark on conntrack. Here
packets with direction IP_CT_DIR_ORIGINAL are marked with 1 and packets with
direction IP_CT_DIR_REPLY are marked with 2. Now as eth0 and eth1 are served
by different CPUs, is there chances of m connmark will get wrong values of
conntrack mark ?
Rgds,
Nishit Shah
next reply other threads:[~2008-02-29 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 10:42 Nishit Shah [this message]
2008-02-29 12:17 ` Accessing conntrack memory on multicore machine Patrick McHardy
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='005001c87abf$d328d570$797a8050$@com' \
--to=nishit@elitecore.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@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.