From: watermodem <aquamodem@ameritech.net>
To: linux-kernel@vger.kernel.org
Subject: Symptoms of overload on Southbridge <-> Northbridge
Date: Tue, 13 Aug 2002 23:54:48 -0500 [thread overview]
Message-ID: <3D59E298.8060604@ameritech.net> (raw)
This question is not truly a kernel question but it has kernel
attributes so I decided to ask it here.
I have some measurement situations (using P-3 and P-4) machines where
the Southbridge to Northbridge connection could get saturated and maybe
even hit the bandwidth limits. These machines are usually older
uni-processor Dells with one flavor or another of Intel chipset.
What sort of hardware symptoms can I expect to see when the bus overloads?
(I am not that worried if the OS crashes but am worried about possible
hardware damage - heat, out of sequence drive commands etc...)
The machines will have 1 gigabit ethernet taking a full sniffer port
load from a loaded CISCO 6509 switch and many more 100Mbit ethernets,
several sniffing and the rest communicating. (Adaptec 4 port units) I
know that is an insane load but we have hundreds of labs many being near
idle most of the time. The mainly near idle labs could use the cheaper
equipment. It would be nice if there was a way to sense nearing overload
and dynamically "throttle down". Would any of the /proc provided
statistics give me the clues I am looking for?
Thanks...
reply other threads:[~2002-08-14 4:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D59E298.8060604@ameritech.net \
--to=aquamodem@ameritech.net \
--cc=linux-kernel@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