From: Sergei Organov <osv@javad.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Scheduler lock in Doug Lea's malloc implementation - be real careful
Date: Mon, 11 Sep 2006 11:11:00 -0000 [thread overview]
Message-ID: <ee3g6r$hoh$1@sea.gmane.org> (raw)
In-Reply-To: <W587588051186621157959860@webmail11>
bob.koninckx@o-3s.com writes:
[...]
> Any comments ? Am I making a fundamental reasoning error here ? If
> not, I am going to try to change the implementation and see if it
> solves our problem and propose a patch.
I believe mutex is better choice for protection of the allocator. The
mutex code indeed disables scheduler, but for very short (and
deterministic) periods of time compared to the time required for
malloc(), so using mutex instead of scheduler lock should solve the
problem.
--
Sergei.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2006-09-11 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 7:31 [ECOS] " bob.koninckx
2006-09-11 11:01 ` Bart Veer
2006-09-11 11:11 ` Sergei Organov [this message]
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='ee3g6r$hoh$1@sea.gmane.org' \
--to=osv@javad.com \
--cc=ecos-discuss@sources.redhat.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).