[PATCH] parallelize bootstrap

Gedare Bloom gedare at rtems.org
Wed Aug 14 18:05:45 UTC 2013


Hi,

Would it be better to add an option to specify the maximum number of
parallel jobs to run? Also, is it 10 jobs or 20 jobs maximum right
now? I think there can be up to 10 controlled by n_confs, and up to 10
controlled by n_reconfs?

-Gedare

On Fri, Aug 2, 2013 at 2:49 AM, Rempel, Cynthia
<cynt6007 at vandals.uidaho.edu> wrote:
> Hi,
>
> Applying this patch changes the for loops using autoconf into parallel for loops calling autoconf.
> It reduced the time to run bootstrap from ~9:30 to ~2:45
> It's limited to 10 sub shells working in parallel though...
> I only checked that hello.exe and ticker.exe ran on sparc-rtems4.11-gdb...
>
> Thanks!
> Cindy
> ________________________________________
> From: rtems-devel-bounces at rtems.org [rtems-devel-bounces at rtems.org] on behalf of Sebastian Huber [sebastian.huber at embedded-brains.de]
> Sent: Thursday, August 01, 2013 11:38 PM
> To: Ashi
> Cc: rtems-devel at rtems.org
> Subject: Re: [PATCH] posix: Reimplement POSIX Key manager to use a red-black tree.
>
> On 2013-08-02 03:03, Ashi wrote:
>>
>>         +  /** This field points to parent freechain node */
>>         +  POSIX_Keys_Freechain_node *fc_node_ptr;
>>
>>
>>     I don't think we need this fc_node_ptr.
>>
>> Do you mean use a 'Container' macro instead?
>
> Not necessarily, see below.
>
>>
>>
>>         +  /** This field is the POSIX key used as an rbtree key */
>>         +  pthread_key_t key;
>>         +  /** This field is the Thread id also used as an rbtree key */
>>         +  Objects_Id thread_id;
>>         +  /** This field points to the POSIX key value of specific thread */
>>         +  void *value;
>>         +}  POSIX_Keys_Rbtree_node;
>>
>>
>>     I would call this POSIX_Keys_Key_value_pair.
>>
>>         +
>>         +/**
>>         + * @brief POSIX_Keys_Freechain is used in Freechain structure
>>         + */
>>         +typedef struct {
>>         +    Freechain_Control super_fc;
>>         +    size_t bump_count;
>>         +} POSIX_Keys_Freechain;
>>         +
>>         +/**
>>         + * @brief POSIX_Keys_Freechain_node is freechain node
>>         + */
>>         +struct POSIX_Keys_Freechain_node___struct {
>>         +  Chain_Node ch_node;
>>         +  POSIX_Keys_Rbtree_node rb_node;
>>         +};
>>
>>
>>     Why not use POSIX_Keys_Rbtree_node directly?
>>
>> Since every freechain node needs a Chain_Node in its first field. There is a
>> Chain_Node in  POSIX_Keys_Rbtree_node, but it is used in each thread's key
>> value chain. So I add a Chain_Node to POSIX_Keys_Rbtree_node.
>
> The key value pairs on the free chain are unused, thus not part of other data
> structures.  So basically you can cast an unused object to any type provided it
> has enough storage.
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel
>
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-devel
>




More information about the devel mailing list