From: Hyochang Nam <cannon@postech.ac.kr>
To: netdev@oss.sgi.com
Subject: [Question] SMP for TCP/IP Stack
Date: Wed, 25 Sep 2002 11:27:31 +0900 [thread overview]
Message-ID: <20020925112731.A19934@toad.postech.ac.kr> (raw)
Can Linux Kernel 2.4.X handle two IP Packets at the same time
in a SMP machine which has two CPUs?
I have a SMP machine which equips two Intel Xeon CPUs and two
Intel Gigabit Network Cards. When I sent small IP Packets
to the machine, most of packets are dropped. When I watch
CPU utlization with TOP program, only one CPU shows high value
but the other shows much low value, ie. 10% CPU utlization.
My test shows current IP Stack in Linux Kernel cannot provide
SMP Processing properly. But, some articles said Linux Kernel 2.4
gives true SMP processing. What do you think my problem is?
Best regards,
Hyochang Nam
next reply other threads:[~2002-09-25 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 2:27 Hyochang Nam [this message]
2002-09-25 2:35 ` [Question] SMP for TCP/IP Stack Benjamin LaHaise
2002-09-25 3:11 ` Ben Greear
2002-09-25 19:32 ` Nivedita Singhvi
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=20020925112731.A19934@toad.postech.ac.kr \
--to=cannon@postech.ac.kr \
--cc=netdev@oss.sgi.com \
/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).