From: Ahmed Abdelkhalek <oneshotawp@yahoo.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] pthread processor binding
Date: Thu, 15 Feb 2007 02:28:00 -0000 [thread overview]
Message-ID: <43209.45155.qm@web62004.mail.re1.yahoo.com> (raw)
In-Reply-To: <20070215004531.GB4385@lunn.ch>
It may make sense especially on a heterogeneous MP
platform, where you might want to bind certain threads
that do expensive work on more capable processors, and
other less demanding threads to cheaper cores.
--- Andrew Lunn <andrew@lunn.ch> wrote:
> On Wed, Feb 14, 2007 at 04:07:56PM -0800, Ahmed
> Abdelkhalek wrote:
> > Hi everyone,
> >
> > Some pthread implementations allow binding a
> thread
> > for execution on a particular processor or a set
> of
> > processors (google pthread_pset_bind_np). Are
> there
> > plans to include this in future ecos realeases?
>
> None that i know of. Does this even make sense in an
> RTOS? I've not
> thought about this long enough to answer that
> question...
>
> Anyway feel free to implement it yourself.
>
> Andrew
>
____________________________________________________________________________________
Get your own web address.
Have a HUGE year through Yahoo! Small Business.
http://smallbusiness.yahoo.com/domains/?p=BESTDEAL
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-02-15 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 0:08 Ahmed Abdelkhalek
2007-02-15 0:45 ` Andrew Lunn
2007-02-15 2:28 ` Ahmed Abdelkhalek [this message]
2007-02-15 10:59 ` Nick Garnett
2007-02-15 18:01 ` Ahmed Abdelkhalek
2007-02-15 19:28 ` Andrew Lunn
2007-02-15 13:34 ` Andrew Lunn
2007-02-15 18:05 ` Ahmed Abdelkhalek
2007-02-15 19:31 ` Andrew Lunn
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=43209.45155.qm@web62004.mail.re1.yahoo.com \
--to=oneshotawp@yahoo.com \
--cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).