Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello all, I'm wondering if any of you encountered the following problem.
Recently installed a Centos5 machine on an old Athlon (2000+ or so), and placed it on a network that constantly has about 70 Mbps Internet Traffic (an ISP). The machine had less than 10% of processor active, all the time (monitored it with cacti for a few weeks). All the unwanted services were disabled (boot-time around 10-15 seconds).
Well, the ISP wanted a stronger machine, in order to place a traffic shaper with thousands of tc rules. And I installed Centos5 on a Intel dual-dore machine. The boot-time here is about 10 seconds, and also the unwanted services are disabled.
Now this is very interesting: on the second (much better) machine, the CPU usage is always above 10%, without any traffic shaping or anything, and this gets 20% at 70 Mbps. With 1500 tc rules, the CPU gets 60%. An unseen value, until now, on the servers i've setted up.
I had Centos4 installed on this machine (it was a ROUTER before), it had a traffic shaper with 1500+ rules and *never* had a CPU time bigger than 15%.
Is the bridging code eating these resources? Did any of you encountered this?
Well, i certainly issue "top", and did not find anything. I mean, no process that eats CPU. All of them (top, ps aux) show 0.0 CPU activity, for all the services. CPU is occupied by kernel, that is certain.
The NICs are Realtek RTL-8169 GigaBit (rev 10), as can be seen from lsmod output, in my previous post.
Thanks, syg00, this is the first time I hear that "si" means "System Interrupts". I could not find this in Top manpage and thought it means System usage or something like it.
I was wondering...how can I use sar command to monitor system interrupts? I have the irqbalance service started, might it have something to do with this?
Yeah, you're right - sar probably won't help much. Time for some basic problem determination.
I'd be suspicious that the code (bridging whatever) isn't multiprocessor compliant. Try turning off the extra processor (in the BIOS preferably, or in the kernel itself), and see if the impact goes away.
Either way, you're going to have to find the culprit - start turning things off and see if you can isolate the effect. I was going to suggest vmstat to track it, but I'm now thinking that interrupt count is only the hardware interrupts. Maybe you'll be best running top in batchmode and pipe it to a file so you can correlate any change/effect.
htop may be more useful than top. htop shows processes in real time AND it is scrollable on the screen. That scrolling feature alone makes it much more useful than top and it's a very small utility. Google htop or go search sourceforge.net, I'm sure it's there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.