mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Al Boldi <a1426z@gawab.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] VM: I have a dream...
Date: Mon, 30 Jan 2006 08:35:21 -0500	[thread overview]
Message-ID: <8F530CA8-1AC8-4AE5-8F1E-DC6518BD7D42@mac.com> (raw)
In-Reply-To: <200601301621.24051.a1426z@gawab.com>

On Jan 30, 2006, at 08:21, Al Boldi wrote:
> Bryan Henderson wrote:
>>>> So we know it [single level storage] works, but also that people  
>>>> don't seem to care much for it
>>
>>> People didn't care, because the AS/400 was based on a proprietary  
>>> solution.
>>
>> I don't know what a "proprietary solution" is, but what we had was  
>> a complete demonstration of the value of single level storage, in  
>> commercial use and everything,  and other computer makers (and  
>> other business units of IBM) stuck with their memory/disk split  
>> personality.  For 25 years, lots of computer makers developed lots  
>> of new computer architectures and they all (practically speaking)  
>> had the memory/disk split.  There has to be a lesson in that.
>
> Sure there is lesson here.  People have a tendency to resist  
> change, even though they know the current way is faulty.

Is it necessarily faulty?  It seems to me that the current way works  
pretty well so far, and unless you can prove a really strong point  
the other way, there's no point in changing.  You have to remember  
that change introduces bugs which then have to be located and removed  
again, so change is not necessarily cheap.

>>> With todays generically mass-produced 64bit archs, what's not to  
>>> care about a cost-effective system that provides direct mapped  
>>> access into  linear address space?
>>
>> I don't know; I'm sure it's complicated.
>
> Why would you think that the shortest path between two points is  
> complicated, when you have the ability to fly?

Bad analogy.  This is totally irrelevant to the rest of the discussion.

>> But unless the stumbling block since 1980 has been that it was too  
>> hard to get/make a CPU with a 64 bit address space, I don't see  
>> what's different today.
>
> You are hitting the nail right on it's head here. Nothing moves the  
> masses like mass-production.

Uhh, no, you misread his argument: If there were other reasons that  
this was not done in the past than lack of 64-bit CPUS, then this is  
probably still not practical/feasible/desirable.

Cheers,
Kyle Moffett

--
There is no way to make Linux robust with unreliable memory  
subsystems, sorry.  It would be like trying to make a human more  
robust with an unreliable O2 supply. Memory just has to work.
   -- Andi Kleen



  reply	other threads:[~2006-01-30 13:35 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 18:08 Al Boldi
2006-01-21 18:42 ` Jamie Lokier
2006-01-21 18:46 ` Avi Kivity
2006-01-23 19:52   ` Bryan Henderson
2006-01-25 22:04     ` Al Boldi
2006-01-26 19:18       ` Bryan Henderson
2006-01-27 16:12         ` Al Boldi
2006-01-27 19:17           ` Bryan Henderson
2006-01-30 13:21             ` Al Boldi
2006-01-30 13:35               ` Kyle Moffett [this message]
2006-01-31 15:56                 ` Al Boldi
2006-01-31 16:34                   ` Kyle Moffett
2006-01-31 23:14                     ` Bryan Henderson
2006-01-31 16:34                   ` Lennart Sorensen
2006-01-31 19:23                   ` Jamie Lokier
2006-02-01  4:06                   ` Barry K. Nathan
2006-02-01  9:51                     ` Andrew Walrond
2006-02-01 17:51                       ` Lennart Sorensen
2006-02-01 18:21                         ` Andrew Walrond
2006-02-01 18:25                           ` Lennart Sorensen
2006-02-02 15:11                   ` Alan Cox
2006-02-02 18:59                     ` Al Boldi
2006-02-02 22:33                       ` Bryan Henderson
2006-02-03 14:46                       ` Alan Cox
2006-01-30 16:49               ` Bryan Henderson
2006-01-26  0:03     ` Jon Smirl
2006-01-26 19:48       ` Bryan Henderson
2006-01-22  8:16 ` Pavel Machek
2006-01-22 12:33 ` Robin Holt
2006-01-23 18:03   ` Al Boldi
2006-01-23 18:40     ` Valdis.Kletnieks
2006-01-23 19:26       ` Benjamin LaHaise
2006-01-23 19:40         ` Valdis.Kletnieks
2006-01-23 22:26     ` Pavel Machek
2006-01-22 19:55 ` Barry K. Nathan
2006-01-23  5:23   ` Michael Loftis
2006-01-23  5:46     ` Chase Venters
2006-01-23  8:20       ` Barry K. Nathan
2006-01-23 13:17       ` Jamie Lokier
2006-01-23 20:21         ` Peter Chubb
2006-01-23 15:05     ` Ram Gupta
2006-01-23 15:26       ` Diego Calleja
2006-01-23 16:11         ` linux-os (Dick Johnson)
2006-01-23 16:50           ` Jamie Lokier
2006-01-24  2:08           ` Horst von Brand
2006-01-25  6:13             ` Jamie Lokier
2006-01-25  9:23             ` Bernd Petrovitsch
2006-01-25  9:42               ` Lee Revell
2006-01-25 15:02                 ` Jamie Lokier
2006-01-25 23:24                   ` Lee Revell
2006-01-25 15:05               ` Jamie Lokier
2006-01-25 15:47                 ` Bernd Petrovitsch
2006-01-25 16:09                 ` Diego Calleja
2006-01-25 17:26                   ` Jamie Lokier
2006-01-26 19:13                     ` Bryan Henderson
2006-01-25 23:28                 ` Lee Revell
2006-01-26  1:29                   ` Diego Calleja
2006-01-26  5:01                   ` Jamie Lokier
2006-01-26  5:11                     ` Lee Revell
2006-01-26 14:46                       ` Dave Kleikamp
2006-01-24  2:10           ` Horst von Brand
2006-01-25 22:27         ` Nix
2006-01-26 15:13           ` Denis Vlasenko
2006-01-26 16:23             ` Nix
2006-01-23 20:43       ` Michael Loftis
2006-01-23 22:42         ` Nikita Danilov
2006-01-24 14:36           ` Ram Gupta
2006-01-24 15:04             ` Diego Calleja
2006-01-24 20:59               ` Bryan Henderson
2006-01-24 15:11             ` Nikita Danilov
2006-01-23 22:57         ` Ram Gupta
2006-01-24 10:08         ` Meelis Roos
2006-02-01 13:58 Al Boldi
2006-02-01 14:38 ` Jamie Lokier
2006-02-02 12:26   ` Al Boldi

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=8F530CA8-1AC8-4AE5-8F1E-DC6518BD7D42@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=a1426z@gawab.com \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®