All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gregory Haskins" <ghaskins@novell.com>
To: unlisted-recipients:; (no To-header on input)
Cc: <linux-kernel@vger.kernel.org>, <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 1/2] RT: Preemptible Function-Call-IPI Support
Date: Tue, 31 Jul 2007 10:26:36 -0400	[thread overview]
Message-ID: <46AF0DF9.BA47.005A.0@novell.com> (raw)
In-Reply-To: <20070731092521.GA16177@elte.hu>

>>> On Tue, Jul 31, 2007 at  5:25 AM, in message <20070731092521.GA16177@elte.hu>,
Ingo Molnar <mingo@elte.hu> wrote: 


> as far as the prioritization of function calls goes, _that_ makes sense, 
> but it should not be a separate API but should be done to our normal 
> workqueue APIs. That not only extends the effects of priorities to all 
> current workqueue using kernel subsystems, but also keeps the API more 
> unified. We really dont want to have too many -rt specific APIs.

I just took a look at the workqueue code .  There are two immediate problems that I see:

1) cpu_workqueue_struct->lock is a spinlock_t and will need to become a raw_spinlock_t

2) The lock is held for the duration of the execution of workqueue items.  We will need to revamp this such that new workqueue items can still be queued even while executing others.

Are these acceptable changes?  If so, I will put together a prototype based around this concept.

Regards,
-Greg

  reply	other threads:[~2007-07-31 14:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 21:15 [PATCH 0/2] VFCIPI support v2 Gregory Haskins
2007-07-30 21:15 ` [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins
2007-07-31  9:19   ` Ingo Molnar
2007-07-31  9:21     ` Ingo Molnar
2007-07-31  9:25       ` Ingo Molnar
2007-07-31 14:26         ` Gregory Haskins [this message]
2007-07-31 14:26         ` Gregory Haskins
2007-07-31 20:14           ` Gregory Haskins
2007-07-30 21:15 ` [PATCH 2/2] RT: Add priority inheritance to the VFCIPI facility Gregory Haskins
2007-07-30 21:34 ` [PATCH 0/2] VFCIPI support v2 Daniel Walker
  -- strict thread matches above, loose matches on Subject: below --
2007-07-31 11:44 [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins
2007-07-31 12:11 Gregory Haskins
2007-07-31 14:22 ` Ingo Molnar
2007-07-31 13:24 [PATCH 0/2][RFC] VFCIPI v3 Gregory Haskins
2007-07-31 13:24 ` [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins

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=46AF0DF9.BA47.005A.0@novell.com \
    --to=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.