From: Robert Love <rml@tech9.net>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, rusty@rustcorp.com.au
Subject: Re: [PATCH] Priority-based real-time futexes [Try two, stupid Outlook wrapped it]
Date: 18 Oct 2002 23:18:47 -0400 [thread overview]
Message-ID: <1034997530.16888.271.camel@phantasy> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C7806CAC806@orsmsx116.jf.intel.com>
On Fri, 2002-10-18 at 22:57, Perez-Gonzalez, Inaky wrote:
> I have completed the priority-based futex support; now the code
> behaves well completely, as futex_fd and poll() work as before, but
> priority based. So, tasks that are sleeping on a futex get waken up by
> priority order. This is useful for real-time locking, with most
> benefits being for the NGPT and NPTL thread libraries.
Very useful for real-time tasks...
I did not think NPTL did real-time threads, though?
> - I don't remember if it is safe to call kmalloc with GFP_KERNEL from
> inside an spinlock. Common sense says NO to me - just in case, in
> the areas where I need it, I use GFP_ATOMIC. Any confirmations?
No, it is not safe as then you can sleep and consequently deadlock.
GFP_ATOMIC is the fix but be weary of how much memory you allocate and
make sure you always check for failure and have some course of action
there.
Robert Love
prev parent reply other threads:[~2002-10-19 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 2:57 [PATCH] Priority-based real-time futexes [Try two, stupid Outlook wrapped it] Perez-Gonzalez, Inaky
2002-10-19 3:18 ` Robert Love [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=1034997530.16888.271.camel@phantasy \
--to=rml@tech9.net \
--cc=inaky.perez-gonzalez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
/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