mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: another subtle signals issue
Date: Wed, 12 Feb 2003 13:58:54 -0800	[thread overview]
Message-ID: <200302122158.h1CLwsM24601@magilla.sf.frob.com> (raw)
In-Reply-To: Linus Torvalds's message of  Wednesday, 12 February 2003 13:19:56 -0800 <Pine.LNX.4.44.0302121318250.1096-100000@penguin.transmeta.com>

> Yeah. There's another issue too, which is the "preferred thread" thing. We 
> should probably _prefer_ threads that are interruptible as opposed to 
> threads that are in disk wait, the same way we prefer threads that are not 
> stopped. It might improve throughput.

I am really only concerned with the correctness issues, and don't have much
opinion on optimization choices like this.  It think the tradeoffs on who
it give it to vs the complexity of the scan and such depend heavily on how
many threads you have and what they are doing.

  reply	other threads:[~2003-02-12 21:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0302111356550.1405-100000@penguin.transmeta.com>
2003-02-12  2:06 ` Roland McGrath
2003-02-12  2:45   ` Linus Torvalds
2003-02-12  3:05     ` Daniel Jacobowitz
2003-02-12  3:10       ` Linus Torvalds
2003-02-12  3:23         ` Roland McGrath
2003-02-12  3:38           ` Linus Torvalds
2003-02-12  3:13     ` Roland McGrath
2003-02-12  3:18       ` Linus Torvalds
2003-02-12  3:50         ` Roland McGrath
2003-02-12  4:21           ` Linus Torvalds
2003-02-12 20:12   ` Linus Torvalds
2003-02-12 21:11     ` Roland McGrath
2003-02-12 21:19       ` Linus Torvalds
2003-02-12 21:58         ` Roland McGrath [this message]
2003-02-12 21:42       ` Linus Torvalds
2003-02-12 22:04         ` Roland McGrath

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=200302122158.h1CLwsM24601@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®