Boost logo

Boost :

Subject: Re: [boost] [thread] feature request priority
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2012-01-03 15:09:43


Vicente Botet wrote:
> Stewart, Robert wrote
> > Vicente J. Botet Escriba wrote:
>
> > 3. You could support a portable interface for thread
> > priorities, but you'd need to determine how to normalize
> > thread priorities since different OSes offer different ranges
> > of priority values. It might be that the portable interface
> > provides only partial prioritization support for some
> > platforms, requiring the use of a native API when that's
> > insufficient. That would give some support for portable
> > code, even if a modest utility that might be enough for many
> > applications. Then again, the result might be so anemic that
> > it would never be used.
>
> My first intention was to provide the minimum, so that users
> are able to use the non-portable interface.
> I'm not sure we can provide a useful and portable interface for
> thread priorities, scheduling, .... The user could always
> define a class inheriting from thread_attributes and provide an
> interface that is portable for his application, which is less
> than requiring a portable interface in the generic sens. I will
> try to add an example in the documentation so that the user
> could find inspiration for his own application.

That's a reasonable first step.

> > 4. I wonder if a thread should own its attributes such that
> > clients can query for them later:
> >
> > thread_attributes const &
> > thread::attributes() const;
>
> The user can always associate the passed attributes to the
> thread either passing them as parameters or/and setting them as
> a thread specific pointer.

Yes and no. Consider thread_group: you can't easily associate the attributes with a thread, if you have access to a thread_group and not the code that called add_thread().

BTW, does the patch address creating threads, with attributes, via thread_group::create_thread()?

_____
Rob Stewart robert.stewart_at_[hidden]
Software Engineer using std::disclaimer;
Dev Tools & Components
Susquehanna International Group, LLP http://www.sig.com

________________________________

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk