Re: Patch for pthread get and set affinity

2014-03-06 Thread Joel Sherrill
On 3/6/2014 1:38 AM, Sebastian Huber wrote: > On 2014-03-05 17:31, Gedare Bloom wrote: >> Joel, >> >> On Wed, Mar 5, 2014 at 10:38 AM, Joel Sherrill >> wrote: >>> On 3/5/2014 9:05 AM, Sebastian Huber wrote: On 2014-03-05 15:58, Joel Sherrill wrote: > On Mar 5, 2014 8:33 AM, Sebastian Hub

Re: Patch for pthread get and set affinity

2014-03-05 Thread Sebastian Huber
On 2014-03-05 17:31, Gedare Bloom wrote: Joel, On Wed, Mar 5, 2014 at 10:38 AM, Joel Sherrill wrote: On 3/5/2014 9:05 AM, Sebastian Huber wrote: On 2014-03-05 15:58, Joel Sherrill wrote: On Mar 5, 2014 8:33 AM, Sebastian Huber wrote: > > On 2014-03-05 15:21, Joel Sherrill wrote: > >

Re: Patch for pthread get and set affinity

2014-03-05 Thread Gedare Bloom
Joel, On Wed, Mar 5, 2014 at 10:38 AM, Joel Sherrill wrote: > > On 3/5/2014 9:05 AM, Sebastian Huber wrote: >> On 2014-03-05 15:58, Joel Sherrill wrote: >>> On Mar 5, 2014 8:33 AM, Sebastian Huber >>> wrote: >>> > >>> > On 2014-03-05 15:21, Joel Sherrill wrote: >>> > > We discussed this priv

Re: Patch for pthread get and set affinity

2014-03-05 Thread Joel Sherrill
On 3/5/2014 9:05 AM, Sebastian Huber wrote: > On 2014-03-05 15:58, Joel Sherrill wrote: >> On Mar 5, 2014 8:33 AM, Sebastian Huber >> wrote: >> > >> > On 2014-03-05 15:21, Joel Sherrill wrote: >> > > We discussed this privately when you raised this to me. It should not >> be part >> > > of

Re: Patch for pthread get and set affinity

2014-03-05 Thread Sebastian Huber
On 2014-03-05 15:58, Joel Sherrill wrote: On Mar 5, 2014 8:33 AM, Sebastian Huber wrote: > > On 2014-03-05 15:21, Joel Sherrill wrote: > > We discussed this privately when you raised this to me. It should not be part > > of the scheduler per thread data. lf you do then the data just disap

Re: Patch for pthread get and set affinity

2014-03-05 Thread Joel Sherrill
On Mar 5, 2014 8:33 AM, Sebastian Huber wrote: > > On 2014-03-05 15:21, Joel Sherrill wrote: > > We discussed this privately when you raised this to me. It should not be > > part > > of the scheduler per thread data. lf you do then the data just disappears > > from > > the API perspective when

Re: Patch for pthread get and set affinity

2014-03-05 Thread Sebastian Huber
On 2014-03-05 15:21, Joel Sherrill wrote: We discussed this privately when you raised this to me. It should not be part of the scheduler per thread data. lf you do then the data just disappears from the API perspective when the scheduler doesn't support affinity. It will create a new class of odd

Re: Patch for pthread get and set affinity

2014-03-05 Thread Joel Sherrill
Gedare.. We discussed this privately when you raised this to me. It should not be part of the scheduler per thread data. lf you do then the data just disappears from the API perspective when the scheduler doesn't support affinity. It will create a new class of odd errors at the API level which

Re: Patch for pthread get and set affinity

2014-03-05 Thread Gedare Bloom
I agree with Sebastian. I raised this issue on the other patch that modifies the TCB to include the Cpuset_Control affinity field. That field should be part of the scheduler's per-thread metadata. On Wed, Mar 5, 2014 at 2:25 AM, Sebastian Huber wrote: > On 2014-02-27 14:28, Jennifer Averett wrote

Re: Patch for pthread get and set affinity

2014-03-04 Thread Sebastian Huber
On 2014-02-27 14:28, Jennifer Averett wrote: +int pthread_setaffinity_np( + pthread_t id, + size_t cpusetsize, + const cpu_set_t *cpuset) +{ + Objects_Locationslocation; + POSIX_API_Control *api; + Thread_Control *the_thread; + int

Re: Patch for pthread get and set affinity

2014-02-27 Thread Gedare Bloom
thod. > I agree. >> -Original Message- >> From: rtems-devel-boun...@rtems.org [mailto:rtems-devel- >> boun...@rtems.org] On Behalf Of Jennifer Averett >> Sent: Thursday, February 27, 2014 9:31 AM >> To: Gedare Bloom >> Cc: rtems-devel@rtems.org >> Subject:

RE: Patch for pthread get and set affinity

2014-02-27 Thread Jennifer Averett
-devel- > boun...@rtems.org] On Behalf Of Jennifer Averett > Sent: Thursday, February 27, 2014 9:31 AM > To: Gedare Bloom > Cc: rtems-devel@rtems.org > Subject: RE: Patch for pthread get and set affinity > > I'm sorry I don't follow this question. This patc

Re: Patch for pthread get and set affinity

2014-02-27 Thread Gedare Bloom
f Of Gedare Bloom >> Sent: Thursday, February 27, 2014 9:17 AM >> To: Jennifer Averett >> Cc: rtems-devel@rtems.org >> Subject: Re: Patch for pthread get and set affinity >> >> Same comments from my email on the other thread apply here. Why don't >> you

RE: Patch for pthread get and set affinity

2014-02-27 Thread Jennifer Averett
edu] On > Behalf Of Gedare Bloom > Sent: Thursday, February 27, 2014 9:17 AM > To: Jennifer Averett > Cc: rtems-devel@rtems.org > Subject: Re: Patch for pthread get and set affinity > > Same comments from my email on the other thread apply here. Why don't > you use

Re: Patch for pthread get and set affinity

2014-02-27 Thread Gedare Bloom
Same comments from my email on the other thread apply here. Why don't you use the pthread_attr_setaffinity_np() to set the api->Attributes affinity? -Gedare On Thu, Feb 27, 2014 at 8:28 AM, Jennifer Averett wrote: > > Attached are patches for pthread get and set > affinity, as well as a test for