From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ULI 2.6.12
Date: Mon, 04 Apr 2005 07:09:57 +0000 [thread overview]
Message-ID: <20050404070957.GA4548@infradead.org> (raw)
In-Reply-To: <20050401130602.A123752@goliath.americas.sgi.com>
On Mon, Apr 04, 2005 at 10:22:37AM +1000, Peter Chubb wrote:
> However, I think that the thing that bothers me *most* about SGI's ULI
> approach is that a full context switch is not done. The ULI runs as
> if it were in the interrupted process's context. `current' isn't
> changed, so it runs with the privileges of the interrupted process.
> The *way* it runs (CPU bound, presumably) will affect the scheduler's
> decisions about how to run the interrupted process in the next
> timeslice. For most interrupt handlers this won't matter, but it'd be
> relatively easy to construct a malicious one to slow particular
> processes.
I agree. Raymonds version looks like a hack for a very narrow special
case to me. I really prefer your more portable and useful version, and
I don't think the performance differences matter given today hardware.
next prev parent reply other threads:[~2005-04-04 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 19:06 [PATCH] ULI 2.6.12 Michael Raymond
2005-04-04 0:22 ` Peter Chubb
2005-04-04 7:09 ` Christoph Hellwig [this message]
2005-04-04 13:31 ` Michael Raymond
2005-04-04 13:45 ` Christoph Hellwig
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=20050404070957.GA4548@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@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