From: "Brian D. McGrew" <brian@visionpro.com>
To: <linux-kernel@vger.kernel.org>
Subject: Memset very slow
Date: Thu, 03 Feb 2011 11:43:46 -0800 [thread overview]
Message-ID: <C9704572.4797C%brian@visionpro.com> (raw)
Hello All!
We're using Dell T5500 workstations and a kernel-2.6.18.194 in CentOS
5.5_x86-64. When we get these Dells, we have to flash the BIOS back to rev
A02 or else everything is so slow its unusable. Now, the "new" T5500's are
here and we don't have the option to flash the BIOS back to A02 since it's a
faster processor and memory and a new motherboard.
We do memset in lots of places in our code, and in a couple places, the
memset is as large as 3GB. Using the old machines with old BIOS, we were
fine but with a newer (current) BIOS on the new machines or the old
machines, memset is so slow it renders the system unusable. But also after
using memset and that taking too long, everything else is slow, especially
system() calls.
On a properly configured "old" machine with the "old" BIOS, I can memset
3GBx2 in about .45 seconds and system calls return in under .25 seconds.
However, sing the new BIOS on either machine, that same memset takes about
20 seconds and system calls 6 to 7 seconds.
I grabbed the bleeding edge 2.6.37 from Elrepo and everything works fine,
new or old boxes and/or BIOS.
So, my question is, can someone explain to me what is going on here? I am
not convinced this is a kernel problem just because a new kernel fixed it;
but, if there were changes related to this in the kernel, then what is the
oldest version I should be looking at to fix my issues?
Thanks!
-brian
next reply other threads:[~2011-02-03 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 19:43 Brian D. McGrew [this message]
2011-02-03 21:31 ` Memset very slow Alan Cox
2011-02-03 21:58 ` Brian D. McGrew
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 21:30 Xose Vazquez Perez
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=C9704572.4797C%brian@visionpro.com \
--to=brian@visionpro.com \
--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