This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: How to "atomize" the end of a thread...
- To: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Subject: Re: [ECOS] How to "atomize" the end of a thread...
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Thu, 04 Oct 2001 21:15:32 +0100
- Cc: 'Robin Farine' <acnrf at dial dot eunet dot ch>,"Ecos-List (E-mail)" <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <B1F6452C89AFD411AE0800A0CC734C230150F9@EMAIL1>
Fabrice Gautier wrote:
>
> > -----Original Message-----
> > From: Robin Farine [mailto:acnrf@dial.eunet.ch]
> > Subject: Re: [ECOS] How to "atomize" the end of a thread...
> >
> >
> > You could reclaim thread1's resources from another thread
> > after making sure that
> > thread1 has entered the EXITED state, so you don't need the
> > atomic termination
> > of thread1.
>
> Yes, but that means I need either a thread doing only that... that doesn't
> fit well in my stuf...
>
> No in fact I think I need an ASR... (This wasn't here a year ago, just seen
> that....) or the priority=0 trick.
>
> But i can't find any doc on the ASRs, Just that they are run from the
> scheduler
They're not very flexible at this stage, and so aren't intended for general
application use yet. But they're designed to solve a different problem:
running code in the context of a thread "before" that thread is
rescheduled. They don't prevent pre-emption.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine