public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rafael Rodríguez Velilla <rrv@tid.es>
To: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] cyg_scheduler_lock
Date: Wed, 23 May 2001 10:53:00 -0000	[thread overview]
Message-ID: <3B0BF367.AAE5362@tid.es> (raw)
In-Reply-To: <3B0BF3D2.EA5B0159@redhat.com>

> >   If I lock the scheduler during the thread then no DSR can occur, no
> > other thread can gain the CPU.
> >   Is it safe to use cyg_scheduler_lock or unlock inside a DSR?
>
> Yes they are safe in a DSR as long as they are balanced (you only lock as
> many as you unlock).

  But it must be balanced in each DSR, isn't it? And this makes it completely
unuseful to use this inside DSRs.


  reply	other threads:[~2001-05-23 10:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23  9:41 Rafael Rodríguez Velilla
2001-05-23 10:31 ` Jonathan Larmour
2001-05-23 10:53   ` Rafael Rodríguez Velilla [this message]
2001-05-23 11:38     ` Jonathan Larmour
2001-05-24  4:55       ` Rafael Rodríguez Velilla
2001-05-24  5:49         ` Hugo Tyson
2001-05-23 10:45 ` Hugo 'NOx' Tyson

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=3B0BF367.AAE5362@tid.es \
    --to=rrv@tid.es \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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).