From: Pavel Machek <pavel@suse.cz>
To: Andi Kleen <ak@suse.de>
Cc: Ivan Godard <igodard@pacbell.net>, linux-kernel@vger.kernel.org
Subject: Re: Kernel support for peer-to-peer protection models...
Date: Mon, 29 Mar 2004 17:36:06 +0200 [thread overview]
Message-ID: <20040329153606.GA3084@openzaurus.ucw.cz> (raw)
In-Reply-To: <20040329011416.591ad315.ak@suse.de>
Hi!
> > > Overall it sounds like your architecture is not very well suited to
> > > run Linux.
> >
> > We believe we can adopt the Linux protection model (i.e. the 386 protection
> > model) with no more work than any other port to a new architectire (ahem).
>
> Just FYI - Linux has been ported to several architectures with similar SASOS
> capabilities in hardware (IA64 or ppc64 on iseries) and they have all opted to use
> an conventional protection model.
>
It might be actually plus for Ivan: if ia64 and ppc64 benefit from
changes for mill, it makes them more acceptable.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2004-03-30 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <048e01c413b3$3c3cae60$fc82c23f@pc21.suse.lists.linux.kernel>
2004-03-27 6:29 ` Kernel support for peer-to-peer protection models Andi Kleen
2004-03-28 20:21 ` Ivan Godard
2004-03-28 23:14 ` Andi Kleen
2004-03-29 8:09 ` Ivan Godard
2004-03-29 15:36 ` Pavel Machek [this message]
2004-03-30 14:06 ` Andi Kleen
2004-03-30 15:09 ` Ivan Godard
[not found] <048e01c413b3_3c3cae60_fc82c23f@pc21>
2004-03-27 10:34 ` Pavel Machek
2004-03-28 1:32 ` Ivan Godard
2004-03-28 6:24 ` Pavel Machek
2004-03-28 6:32 ` Ivan Godard
2004-03-28 18:54 ` Pavel Machek
2004-03-28 19:56 ` Ivan Godard
2004-03-28 20:35 ` Pavel Machek
2004-03-27 4:23 Ivan Godard
2004-03-29 0:17 ` Paul Mackerras
2004-03-29 3:18 ` Ivan Godard
2004-03-29 3:48 ` Davide Libenzi
2004-03-29 7:52 ` Ivan Godard
2004-03-29 18:45 ` Davide Libenzi
2004-03-29 20:53 ` Ivan Godard
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=20040329153606.GA3084@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=igodard@pacbell.net \
--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