From: Ryan Cumming <bodnar42@phalynx.dhs.org>
To: vvikram@av.stanford.edu, linux-kernel@vger.kernel.org
Subject: Re: [ingo patch] 2.4.17 benchmarks
Date: Sun, 6 Jan 2002 02:17:30 -0800 [thread overview]
Message-ID: <E16NAMs-0000kv-00@phalynx> (raw)
In-Reply-To: <20020105215048.A9335@av.stanford.edu>
In-Reply-To: <20020105215048.A9335@av.stanford.edu>
On January 5, 2002 21:50, vvikram@av.stanford.edu wrote:
> 2) further i seperately ran ./lat_proc fork; ./lat_proc exec; ./lat_proc
> shell many times on the vanilla and patched kernels. their output is also
> attached in one file [lat_proc.txt]. the patched kernel takes
> MORE time than the vanilla one......
I'd blame this partially on the reverted fork() execution order bit of his
patch. The child process really should be executed first, and performance is
much improved in that case (COW and things). I don't think we should worry
about breaking obviously incorrect (and already fragile) programs for 2.5.x.
-Ryan
next prev parent reply other threads:[~2002-01-06 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 5:50 [ingo patch] 2.4.17 benchmarks vvikram
2002-01-06 10:17 ` Ryan Cumming [this message]
2002-01-06 12:34 ` Vikram
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=E16NAMs-0000kv-00@phalynx \
--to=bodnar42@phalynx.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vvikram@av.stanford.edu \
/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