From: Gary Thomas <gary@chez-thomas.org>
To: George Sosnowski <george@stratalight.com>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] malloc/new in DSRs
Date: Thu, 11 Jul 2002 14:18:00 -0000 [thread overview]
Message-ID: <1026422284.27291.7214.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <F626113795D3EB4482E5ACFBD93465121361A4@mailhost.stratalight.com>
On Thu, 2002-07-11 at 15:04, George Sosnowski wrote:
> If malloc is configed to be threadsafe in ecos.ecc, then is it ok to use
> malloc/new/free/delete in DSRs?
> I assume it is, but want to make sure.
I would not think so. DSR's are not allowed to "block" and if
you got into the DSR while inside some thread-safe protected code
(i.e. protected by a semaphore or mutex), it might try to.
Calling malloc() and friends from DSR code is normally considered poor
practice anyway. Why would you think you need to?
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-07-11 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 14:04 George Sosnowski
2002-07-11 14:18 ` Gary Thomas [this message]
2002-07-29 16:22 ` Bart Veer
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=1026422284.27291.7214.camel@hermes.chez-thomas.org \
--to=gary@chez-thomas.org \
--cc=ecos-discuss@sources.redhat.com \
--cc=george@stratalight.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).