mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiachen Dong <xiachendong@hotmail.com>
To: <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.36 and higher version kernel slower than 2.6.25.1 kernel?
Date: Wed, 7 Mar 2012 14:59:35 -0500	[thread overview]
Message-ID: <BAY167-W127BF20C0952D601BC4381FBD560@phx.gbl> (raw)
In-Reply-To: <20120307194728.GA26341@kroah.com>


Thanks for your reply.

There could be quite some code change from 2.6.25.1 to 2.6.36. What we are doing now is to find the first version starting from 2.6.25.1 that has the performance hit. Then we start comparing the code and see what's changed. Looks like 2.6.28.7 is OK.

Haven't tried 3.2.29 yet because 3.2.29 probably won't be available in the BSP from our board manufacturer in the near future. I'll try 3.2.29 tonight on X86 CPU  anyway and get you updated.

Thanks,

Xiachen

----------------------------------------
> Date: Wed, 7 Mar 2012 11:47:28 -0800
> From: gregkh@linuxfoundation.org
> To: xiachendong@hotmail.com
> CC: linux-kernel@vger.kernel.org
> Subject: Re: 2.6.36 and higher version kernel slower than 2.6.25.1 kernel?
>
> On Wed, Mar 07, 2012 at 12:04:33PM -0500, Xiachen Dong wrote:
> >
> > Hi,
> >
> > Recently we upgrade the OS for our AT91RM9200 platform from 2.6.25.1
> > to 2.6.36. We run the SQLITE3 database insertion tests for the new
> > kernel. The test result shows that 2.6.36 kernel is around 10% slower
> > than the 2.6.25.1.
>
> Ick.
>
> As you noted this is still present in 3.0.23, any chance to try out
> 3.2.9?
>
> And as you seem to have a good reproducable test, can you run 'git
> bisect' between 2.6.35 and 2.6.36 to find the patch that causes this
> problem so we can work on resolving it?
>
> thanks,
>
> greg k-h
 		 	   		  

  reply	other threads:[~2012-03-07 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 17:04 Xiachen Dong
2012-03-07 19:47 ` Greg KH
2012-03-07 19:59   ` Xiachen Dong [this message]
2012-03-07 20:06     ` Greg KH

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=BAY167-W127BF20C0952D601BC4381FBD560@phx.gbl \
    --to=xiachendong@hotmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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

all inboxes | Powered by JetHome®