Skip to contentSkip to conversation

FC2 + PowerEdge 2650 + smp kernel + iptables rules loading slow

DISCUSSION Iulian Topliceanu 4 participants 6 messages Dec 7, 2004 – Dec 8, 2004

lore
Share & tools
lore
#0 lore raw

Hi,

I recently noticed the following:

OS: FC2
Kernel: 2.6.8smp and 2.6.8
Hardware: Dell PowerEdge with 2 x 2.8 CPUs, 2 GB RAM etc. iptables version: iptables-1.2.9-2.3.1

The thing is:

1 - when booting a 2.6.8smp kernel (and as well 2.6.Xsmp) it takes about 1 min and 25 seconds to load 114 iptables rules.

2 - when booting a 2.6.8 kernel (so without smp) it only takes 20 seconds to load the same rules.

I've tried several iptables verions but the results were the same.

The question: why? :)

I know that there was a bug regarding Dell PowerEdge 2650 and FC1 with smp kernels (the machine wasn't booting) but does now anyone have a clue where to look or how to solve this issue?

It's a waste to use e dual CPU machine with a non-smp kernel and I'm not allowed to install another OS because of the company policies.

Thanks for you support,
Iulian Topliceanu

#1 lore raw
Quoted 15 lines · Iulian Topliceanu

Hi,

I recently noticed the following:

OS: FC2
Kernel: 2.6.8smp and 2.6.8
Hardware: Dell PowerEdge with 2 x 2.8 CPUs, 2 GB RAM etc. iptables version: iptables-1.2.9-2.3.1

The thing is:

1 - when booting a 2.6.8smp kernel (and as well 2.6.Xsmp) it takes about 1 min and 25 seconds to load 114 iptables rules.

2 - when booting a 2.6.8 kernel (so without smp) it only takes 20 seconds to load the same rules.

Quoted 7 lines

I've tried several iptables verions but the results were the same.

The question: why? :)

I know that there was a bug regarding Dell PowerEdge 2650 and FC1 with smp kernels (the machine wasn't booting) but does now anyone have a clue where to look or how to solve this issue?

It's a waste to use e dual CPU machine with a non-smp kernel and I'm not allowed to install another OS because of the company policies.

Maybe you should ask on the netfilter newsgroup.

Quoted 3 lines

Thanks for you support,
Iulian Topliceanu

#2 lore raw
Quoted 5 lines

Maybe you should ask on the netfilter newsgroup.

Sorry, I thought I was on another newsgroup.

My apologies.

Ugo

#3 lore raw
In reply to Iulian Topliceanu
Quoted 8 lines · Iulian Topliceanu

Hi,

I recently noticed the following:

OS: FC2
Kernel: 2.6.8smp and 2.6.8
Hardware: Dell PowerEdge with 2 x 2.8 CPUs, 2 GB RAM etc. iptables version: iptables-1.2.9-2.3.1

isn't the latest FC2 kernel 2.6.9-1.6? i would go ahead and try that, as i had nothing but problems with the 2.6.8 FC2 kernels.

did you have this problem with 2.6.7 as well?

-j

--
"Here we have an ordinary square.
Whoa! Slow down egghead!"
--The Simpsons

#4 lore raw
Quoted 14 lines · Jason Opperisano
Quoted 10 lines · Iulian Topliceanu

Hi,

I recently noticed the following:

OS: FC2
Kernel: 2.6.8smp and 2.6.8
Hardware: Dell PowerEdge with 2 x 2.8 CPUs, 2 GB RAM etc. iptables version: iptables-1.2.9-2.3.1

Quoted 6 lines

isn't the latest FC2 kernel 2.6.9-1.6? i would go ahead and try that, as i had nothing but problems with the 2.6.8 FC2 kernels.

did you have this problem with 2.6.7 as well?

I've tried 2.6.5, 2.6.7, 2.6.8 and 2.6.9. All smp.

I did not notice any changes.

Regards,
Iulian

#5 lore raw
In reply to Iulian Topliceanu
Quoted 3 lines

I've tried several iptables verions but the results were the same.

The question: why? :)

just first guess.

are not you trying to add rules which use DNS or other name system names instead of IP addresses?
(before the name system is availaible(notwork down) or after name system become unavailaible(iptables policies and rules))