From: root@smtp.nexlab.net
To: undisclosed-recipients:;
Date: Tue, 24 May 2005 11:21:18 +0200 (CEST) [thread overview]
Message-ID: <20050524092118.4F404FA75@smtp.nexlab.net> (raw)
by smtp.nexlab.net (Postfix) with ESMTP id 399D6FB6B
for <chiakotay@nexlab.it>; Tue, 24 May 2005 10:01:40 +0200 (CEST)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S261300AbVEXCDR (ORCPT <rfc822;chiakotay@nexlab.it>);
Mon, 23 May 2005 22:03:17 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261299AbVEXCDR
(ORCPT <rfc822;linux-kernel-outgoing>);
Mon, 23 May 2005 22:03:17 -0400
Received: from mail.timesys.com ([65.117.135.102]:23125 "EHLO
exchange.timesys.com") by vger.kernel.org with ESMTP
id S261300AbVEXCDO (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
Mon, 23 May 2005 22:03:14 -0400
Received: from [127.0.0.1] ([192.168.2.230]) by exchange.timesys.com with Microsoft SMTPSVC(5.0.2195.6713);
Mon, 23 May 2005 21:56:39 -0400
Message-ID: <42928AFF.7010503@timesys.com>
Date: Mon, 23 May 2005 22:01:35 -0400
From: john cooper <john.cooper@timesys.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dwalker@mvista.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, akpm@osdl.org,
sdietrich@mvista.com, john cooper <john.cooper@timesys.com>
Subject: Re: RT patch acceptance
References: <1116890066.13086.61.camel@dhcp153.mvista.com>
In-Reply-To: <1116890066.13086.61.camel@dhcp153.mvista.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 May 2005 01:56:41.0000 (UTC) FILETIME=[D4209280:01C56003]
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
Daniel Walker wrote:
> I went to see Andrew Morton speak at Xerox PARC and he indicated that
> some of the RT patch was a little crazy . Specifically interrupts in
> threads (Correct me if I'm wrong Andrew). It seems a lot of the
> maintainers haven't really warmed up to it.
Understandably at first encounter it may seem rather
unconventional. However scheduled interrupt execution
has existed in Solaris for years.
What are the objections?
-john
--
john.cooper@timesys.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2005-05-24 9:43 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=20050524092118.4F404FA75@smtp.nexlab.net \
--to=root@smtp.nexlab.net \
/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®