From: Tim Verhoeven <tim.verhoeven.be@gmail.com>
To: "bdschuym@pandora.be" <bdschuym@telenet.be>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Compiling ebtables statically or dynamically results in different behaviour
Date: Wed, 8 Apr 2009 11:57:38 +0200 [thread overview]
Message-ID: <2a7fce340904080257r4164cd63hcd5f07b036489aae@mail.gmail.com> (raw)
In-Reply-To: <W8403423488155181239184148@nocme1bl6.telenet-ops.be>
On Wed, Apr 8, 2009 at 11:49 AM, bdschuym@pandora.be
<bdschuym@telenet.be> wrote:
> What is your exact command and what type of processor are you using?
>
The command run is "ebtables -N 1000"
This is /proc/cpuinfo :
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
stepping : 6
cpu MHz : 2666.758
cache size : 6144 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc
pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
bogomips : 6669.91
clflush size : 64
cache_alignment : 64
address sizes : 38 bits physical, 48 bits virtual
It's a standard Intel Xeon (the server is a IBM HS21 Blade).
Regards,
Tim
--
Tim Verhoeven - tim.verhoeven.be@gmail.com - 0479 / 88 11 83
Hoping the problem magically goes away by ignoring it is the
"microsoft approach to programming" and should never be allowed.
(Linus Torvalds)
next prev parent reply other threads:[~2009-04-08 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 9:49 Compiling ebtables statically or dynamically results in different behaviour bdschuym@pandora.be
2009-04-08 9:57 ` Tim Verhoeven [this message]
2009-04-20 9:27 ` Tim Verhoeven
2009-04-20 17:43 ` Bart De Schuymer
-- strict thread matches above, loose matches on Subject: below --
2009-04-07 13:53 Tim Verhoeven
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=2a7fce340904080257r4164cd63hcd5f07b036489aae@mail.gmail.com \
--to=tim.verhoeven.be@gmail.com \
--cc=bdschuym@telenet.be \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).