Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dongxiao Xu <dongxiao.xu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1][RFC] libc locale split
Date: Wed,  8 Jun 2011 17:08:31 +0800	[thread overview]
Message-ID: <cover.1307523829.git.dongxiao.xu@intel.com> (raw)

Hi Richard and Saul,

This pull request split the libc-locale from libc recipe, which can improve the build performance.
Please help to review and pull.

Some test results: 

CPU: Intel i7 870 CPU.
Memory: 4G.
Image: core-image-sato.
Machine: qemux86.

W/o the patch:
real    111m52.954s
user    367m56.610s
sys     49m20.770s

W/ the patch:
real    105m25.436s
user    372m48.040s
sys     51m23.950s

There are about 6% performance gain.

Thanks,
Dongxiao

The following changes since commit 5af197b55a4b779f1ec93186f0723026949ba2b5:

  cache: Implement multiple extra cache fields request support (2011-06-07 22:40:01 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dxu4/libc-locale
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/libc-locale

Dongxiao Xu (1):
  libc-locale: split locale handling from libc recipe.

 meta/classes/libc-common.bbclass                   |   23 ++++++++
 meta/classes/libc-package.bbclass                  |   24 --------
 meta/conf/distro/include/tclibc-eglibc.inc         |   12 ++--
 meta/conf/distro/include/tclibc-glibc.inc          |   12 ++--
 meta/recipes-core/eglibc/eglibc-initial_2.13.bb    |    4 ++
 meta/recipes-core/eglibc/eglibc-locale_2.13.bb     |   56 ++++++++++++++++++++
 meta/recipes-core/eglibc/eglibc-package.inc        |   32 +----------
 meta/recipes-core/eglibc/eglibc.inc                |    5 +-
 meta/recipes-core/eglibc/eglibc_2.13.bb            |   12 ++++
 meta/recipes-core/glibc/glibc-initial_2.10.1.bb    |    4 ++
 meta/recipes-core/glibc/glibc-locale_2.10.1.bb     |   48 +++++++++++++++++
 meta/recipes-core/glibc/glibc-package.inc          |   31 ++---------
 meta/recipes-core/glibc/glibc.inc                  |    2 +-
 meta/recipes-core/glibc/glibc_2.10.1.bb            |   12 ++++
 .../meta/external-csl-toolchain_2008q3-72.bb       |    3 +-
 meta/recipes-core/meta/external-poky-toolchain.bb  |    2 +-
 meta/recipes-gnome/gtk+/gtk+.inc                   |    2 +-
 17 files changed, 187 insertions(+), 97 deletions(-)
 create mode 100644 meta/classes/libc-common.bbclass
 create mode 100644 meta/recipes-core/eglibc/eglibc-locale_2.13.bb
 create mode 100644 meta/recipes-core/glibc/glibc-locale_2.10.1.bb




             reply	other threads:[~2011-06-08  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  9:08 Dongxiao Xu [this message]
2011-06-08  9:08 ` [PATCH 1/1] libc-locale: split locale handling from libc recipe Dongxiao Xu
2011-06-08  9:36   ` Phil Blundell
2011-06-08 15:35     ` Richard Purdie
2011-06-09 11:14       ` Phil Blundell
2011-06-09 11:29         ` Richard Purdie
2011-06-09 11:43           ` Phil Blundell
2011-06-09 13:15             ` Richard Purdie
2011-06-09 13:51               ` Richard Purdie
2011-06-09 13:53               ` Koen Kooi
2011-06-09 13:55                 ` Phil Blundell

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=cover.1307523829.git.dongxiao.xu@intel.com \
    --to=dongxiao.xu@intel.com \
    --cc=openembedded-core@lists.openembedded.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