public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Armin Schindler <mac@melware.de>
To: linux-kernel@vger.kernel.org
Subject: Q: tq_scheduler slower on SMP ?
Date: Sun, 3 Dec 2000 15:40:05 +0100	[thread overview]
Message-ID: <00120315500101.18928@cops> (raw)

Hi,

with kernel 2.2.17 I need to have a
function in my driver to handle some data.
I used BH with tq_immediate, but I found
out, that my function need to be called
outside of interrupt context, but still as
soon as I need it. 
So I decided to use the tq_scheduler queue and
put my function on the task_queue in my interrupt handler.
It seems to work good without SMP, but with SMP
my function is called with delays of many msecs.

Since the tq_scheduler queue is only started from
schedule(), do I need to set some flag to run schedule
asap ?
Or has someone better idea for my function ?

Thanx,

Armin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-12-03 15:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=00120315500101.18928@cops \
    --to=mac@melware.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox