From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading from Buildroot 0.10 to 2009.08 (ARM)
Date: Sun, 08 Nov 2009 22:50:03 +0100 [thread overview]
Message-ID: <87my2wu1o4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <op.u20sibi9yqa4qb@jap-lappis.nevion.com> (Joachim Pihl's message of "Sat\, 7 Nov 2009 11\:24\:01 +0100")
>>>>> "Joachim" == Joachim Pihl <jpihl@nevion.com> writes:
Hi,
>> Yes, NTPL support in uclibc is still very much work in progress.
Joachim> Just before I left work yesterday, I discovered that the uclibc
Joachim> .config (inherited from previous project) had "use linuxthreads" set,
Joachim> while buildroot had NPTL set. The mismatch here could be what we are
Joachim> looking for?
No, buildroot rewrites that part of the uclibc config (see
toolchain/uClibc/uclibc.mk)
Joachim> I would much prefer NPTL if it works, since our applications
Joachim> are heavily multithreaded (for architecture clarity reasons,
Joachim> among other things), and I suspect that some of the
Joachim> performance issues we have could be caused by context
Joachim> switch/scheduling latency.
You should probably check on the uclibc list, but there's afaik no NPTL
support for any architecture in any released uclibc versions.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-11-08 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 7:47 [Buildroot] Upgrading from Buildroot 0.10 to 2009.08 (ARM) Joachim Pihl
2009-11-06 8:52 ` Sven Neumann
2009-11-06 8:59 ` Joachim Pihl
2009-11-06 9:02 ` Sven Neumann
2009-11-06 9:03 ` Joachim Pihl
2009-11-06 9:42 ` Thomas Petazzoni
2009-11-06 9:54 ` Joachim Pihl
2009-11-07 10:08 ` Peter Korsgaard
2009-11-06 9:04 ` Thomas Petazzoni
2009-11-06 9:26 ` Joachim Pihl
2009-11-06 9:53 ` Thomas Petazzoni
2009-11-06 12:16 ` Joachim Pihl
2009-11-06 12:28 ` Joachim Pihl
2009-11-06 12:48 ` Joachim Pihl
2009-11-06 13:02 ` Joachim Pihl
2009-11-07 10:10 ` Peter Korsgaard
2009-11-07 10:24 ` Joachim Pihl
2009-11-08 21:50 ` Peter Korsgaard [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=87my2wu1o4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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