From: Phy Prabab <phyprabab@yahoo.com>
To: "Robert M. Stockmann" <stock@stokkie.net>, linux-kernel@vger.kernel.org
Subject: Re: Help understanding slow down
Date: Sun, 23 May 2004 18:50:00 -0700 (PDT) [thread overview]
Message-ID: <20040524015000.96335.qmail@web90003.mail.scd.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405240325180.15205-100000@hubble.stokkie.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 3656 bytes --]
Robert,
This is a x86 machine which I have transitioned to for
the time being. I had submitted a previous email
discussing the Opteron, however, did not hear back so
tried the x86 tests.
uname -a
Linux c1m12 2.6.7-rc1 #2 SMP Sun May 23 18:16:47 PDT
2004 i686 i686 i386 GNU/Linux
making headers for my custom binary is basically just
making links to all the different header file
scattered within the source code (some dependancy
make).
Phy
--- "Robert M. Stockmann" <stock@stokkie.net> wrote:
> Hi Phy,
>
> Could you also give the uname -a output of both the
> 2.4.x and
> the 2.6.x kernels ? And also mention which make
> options you use ? :
>
> make : 1 thread , load is around 1.00
> make -j 2 : 2 theads , load is around 2.00
> make -j 4 : 4 theads , load is around 4.00
>
> # uname -a (dual-Xeon SMP machine)
> Linux jackson.stokkie.net 2.4.23abi #1 SMP Sun Jan
> 25 03:28:48 CET 2004 i686 unknown unknown GNU/Linux
> ^^^^
>
> # uname -a (poor PII 400 MHz machine)
> Linux tapebox.stokkie.net 2.6.6 #1 Thu May 13
> 05:48:57 CEST 2004 i686 unknown unknown GNU/Linux
> ^^^ no SMP
>
> Also , is your Opteron machine rather different as
> the mainstream Opteron
> boards, i.e. are there some exotic drivers used ?
>
> Regards,
>
> Robert
>
> > Just for more clarification, here is a perfect
> > example:
> >
> > 2.6.7-p1:
> > 24.86user 51.77system 2:58.87elapsed 42%CPU
> > (0avgtext+0avgdata 0maxresident)k
> > 0inputs+0outputs (13major+7591686minor)pagefaults
> > 0swaps
> >
> > 2.4.21:
> > 28.68user 34.98system 1:12.34elapsed 87%CPU
> > (0avgtext+0avgdata 0maxresident)k
> > 0inputs+0outputs
> (5691267major+1130523minor)pagefaults
> > 0swaps
> >
> >
> > Both runs on the same machine with the same
> process
> > (making headers).
> >
> > Could someone give me some pointers/directions on
> > where to look.
> >
> > Thank you for your time.
> > Phy
> >
> > --- Phy Prabab <phyprabab@xxxxxxxxx> wrote:
> >> Hello,
> >>
> >> I need some help understanding what is at issue
> with
> >> the extreme lsow down in build times for a custom
> >> executable on different kernel versions. The
> >> difference is pretty huge:
> >>
> >> RH 2.4.20-13-7 : ~1m.10s
> >> 2.4.22 : ~1m.40s
> >> 2.4.26 : ~2m.15s
> >> 2.6.1 : ~3m.40s
> >> 2.6.2 : ~4m.00s
> >> 2.6.3 : ~4m.00s
> >> 2.6.6 : ~3m.15s
> >> 2.6.6-mm4 : ~2m.10s
> >> 2.6.6-mm5 : ~2m.50s
> >> 2.6.7-p1 : ~2m.80s
> >> (ran five times on every kernel to get
> approximate
> >> time listed)
> >>
> >> The question is, how can I get the newer kernels
> to
> >> scream like the older kernels?
> >>
> >> I have moved all files in question to the local
> disk
> >> to rule out network issues (though the 2.6.x
> kernels
> >> are faster at net access). I have run the make
> >> command in debug mode and find no differnce betHz
> >> w/8G
> >> RAM.
> >>
> >> Thank you for your assistance.
> >> Phy
> >>
> >> __________________________________
> >> Do you Yahoo!?
> >> Yahoo! Domains ? Claim yours for only $14.70/year
> >> http://smallbusiness.promotions.yahoo.com/offer
>
> -
> Robert M. Stockmann - RHCE
> Network Engineer - UNIX/Linux Specialist
> crashrecovery.org stock@stokkie.net
>
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
__________________________________
Do you Yahoo!?
Yahoo! Domains Claim yours for only $14.70/year
http://smallbusiness.promotions.yahoo.com/offer
next prev parent reply other threads:[~2004-05-24 1:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 1:37 Robert M. Stockmann
2004-05-24 1:50 ` Phy Prabab [this message]
2004-05-24 3:31 ` Robert M. Stockmann
2004-05-24 6:14 ` Phy Prabab
2004-05-24 18:36 ` Robert M. Stockmann
-- strict thread matches above, loose matches on Subject: below --
2004-05-24 0:32 Phy Prabab
2004-05-24 0:57 ` Phy Prabab
2004-05-24 1:04 ` William Lee Irwin III
2004-05-24 1:25 ` Jakob Oestergaard
2004-05-24 1:28 ` William Lee Irwin III
2004-05-24 1:51 ` Phy Prabab
2004-05-24 2:42 ` Nick Piggin
2004-05-24 2:43 ` Andrew Morton
2004-05-24 6:23 ` Phy Prabab
2004-05-24 6:27 ` William Lee Irwin III
2004-05-24 6:39 ` Phy Prabab
2004-05-24 7:21 ` Phy Prabab
2004-05-24 7:44 ` Nick Piggin
2004-05-24 7:50 ` Phy Prabab
2004-05-24 7:59 ` Nick Piggin
2004-05-24 10:43 ` Jakob Oestergaard
2004-05-24 14:13 ` Martin J. Bligh
2004-05-24 7:53 ` Andrew Morton
2004-05-24 8:00 ` Phy Prabab
2004-05-25 10:32 ` Ingo Molnar
2004-05-25 9:29 ` Andrew Morton
2004-05-25 11:42 ` Ingo Molnar
2004-05-25 9:58 ` Andrew Morton
2004-05-25 12:25 ` Ingo Molnar
2004-05-24 6:33 ` Paul Rolland
2004-05-24 17:28 ` Roger Luethi
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=20040524015000.96335.qmail@web90003.mail.scd.yahoo.com \
--to=phyprabab@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stock@stokkie.net \
/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
all inboxes | Powered by JetHome®