mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: linux-kernel@vger.kernel.org
Subject: Re: Virtual address space exhaustion (was Discontigmem virt_to_page() )
Date: Sun, 05 May 2002 10:59:03 -0700	[thread overview]
Message-ID: <4237780085.1020596342@[10.10.2.3]> (raw)
In-Reply-To: <200205041944.g44JiEX12535@Port.imtp.ilyichevsk.odessa.ua>

> On 3 May 2002 20:35, Martin J. Bligh wrote:
>> > No. It's not stupid. Unix defines a kind of operating system that
>> > has certain characteristics and/or attributes. Process/kernel shared
>> > address space is one of them. It's a name that has historical
>> > signifigance.
>> 
>> Yes it is stupid. This is a small implementation detail, and has no
>> real importance whatsoever. People have done this in the past
>> (Dynix/PTX did it) will do so in the future. Nor does the kernel
>> address space have to be global and shared across all tasks
>> as stated earlier in this thread. What makes it Unix is the interface
>> it presents to the world, and how it behaves, not the little details
>> of how it's implemented inside.
> 
> I'm curious where it is visible to userspace?
> (I'm asking for educational purposes)

Where what is visible to userspace? If you mean the bit about 
"the interface it presents to the world", I meant Linux in 
general, not this feature. The whole point is that this is 
invisble to userspace (apart from performance and a lack of
architectural restrictions you might have been expecting) 
therefore it's irrelevant to whether it's "Unix" like or not.

M.


  reply	other threads:[~2002-05-05 18:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 18:37 Tony Luck
2002-05-03 19:01 ` Richard B. Johnson
2002-04-27  1:15   ` Pavel Machek
2002-05-03 19:09   ` Christoph Hellwig
2002-05-03 19:17     ` Richard B. Johnson
2002-05-03 19:24       ` Christoph Hellwig
2002-05-03 19:38   ` Matti Aarnio
2002-05-03 19:50   ` Tony Luck
2002-05-03 20:22   ` Jeff Dike
2002-05-03 19:30     ` Richard B. Johnson
2002-05-03 22:35       ` Martin J. Bligh
2002-05-05  0:49         ` Denis Vlasenko
2002-05-05 17:59           ` Martin J. Bligh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-03  8:38 Bug: Discontigmem virt_to_page() [Alpha,ARM,Mips64?] Andrea Arcangeli
2002-05-03 15:17 ` Virtual address space exhaustion (was Discontigmem virt_to_page() ) Martin J. Bligh
2002-05-03 15:58   ` Andrea Arcangeli
2002-05-03 16:10     ` Martin J. Bligh
2002-05-03 16:25       ` Andrea Arcangeli
2002-05-03 16:02   ` Daniel Phillips
2002-05-03 16:20     ` Andrea Arcangeli
2002-05-03 16:41       ` Daniel Phillips
2002-05-03 16:58         ` Andrea Arcangeli
2002-05-03 18:08           ` Daniel Phillips

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='4237780085.1020596342@[10.10.2.3]' \
    --to=martin.bligh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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®