From: Ben Greear <greearb@candelatech.com>
To: Tobias Koeck <tobias.koeck@gmail.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: Performance degradation on 2.6.25 kernels for http servers
Date: Wed, 23 Jul 2008 14:22:58 -0700 [thread overview]
Message-ID: <4887A132.7010407@candelatech.com> (raw)
In-Reply-To: <379e30200807231420n676323a2h6fd760af50f7437f@mail.gmail.com>
Tobias Koeck wrote:
> Do you have the same configuration?
I'm not sure I understand the question.
We were booting into one kernel, running the test, and
then rebooting with a different kernel. There were no other
changes to any config files or settings that I am aware of.
I'll try a git-bisect when I get a chance...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2008-07-23 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 20:37 Performance degradation on 2.6.25 kernels for http servers Ben Greear
2008-07-23 21:20 ` Tobias Koeck
2008-07-23 21:22 ` Ben Greear [this message]
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=4887A132.7010407@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=tobias.koeck@gmail.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).