From: Nick Piggin <npiggin@kernel.dk>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: maciej.rutecki@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Nick Piggin <npiggin@kernel.dk>
Subject: Re: 2.6.37-rc3-git4 bad desktop performance
Date: Tue, 30 Nov 2010 11:04:06 +1100 [thread overview]
Message-ID: <20101130000406.GB3255@amd> (raw)
In-Reply-To: <AANLkTi=ERtG5spFqKH0Xc7JXKrM=YEwyrkb6RsdNbmKH@mail.gmail.com>
On Mon, Nov 29, 2010 at 04:04:56PM +0200, Anca Emanuel wrote:
> Ups, false alarm, sorry. (wrong git tree)
>
> I can reproduce this only with:
> git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git
> vfs-scale-working
What performance is bad? Anything in dmesg? Can you bisect the vfs scale
git tree patches?
prev parent reply other threads:[~2010-11-30 0:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 12:21 2.6.37-rc3-git4 bad desktop performance Anca Emanuel
2010-11-28 15:21 ` Maciej Rutecki
2010-11-28 16:51 ` Anca Emanuel
2010-11-28 20:07 ` Anca Emanuel
2010-11-29 1:36 ` Anca Emanuel
2010-11-29 14:04 ` Anca Emanuel
2010-11-30 0:04 ` Nick Piggin [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=20101130000406.GB3255@amd \
--to=npiggin@kernel.dk \
--cc=anca.emanuel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@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