All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Matthew Wilcox <willy@debian.org>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	"FARINATI, LEANDRO" <leandro.farinati@hp.com>,
	parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 64 userspace
Date: Wed, 15 Jan 2003 13:54:38 -0500	[thread overview]
Message-ID: <20030115185438.GC19253@systemhalted> (raw)
In-Reply-To: <20030115184636.M26554@parcelfarce.linux.theplanet.co.uk>

> > 1) Kernel -- design and implement 64-bit system calls.
> 
> Another piece of the kernelside puzzle is designing the VM layout for
> 64-bit processes.  Do we want to (as ia64 does) reserve parts of the address
> space for the kernel?  Map shared libraries in different quadrants from
> the user process?  Keep data in yet another quadrant?
> 
> It's a lot of work, and I'm not sure the will is there to make it happen.
> 

We are swamped with a 32-bit userspace, and 32/64-bit kernel, creating a
full 64-bit userspace is extremely difficult. I'm currently trying to
workout the bits to get a static 64-bit Glibc, though currently fixing
the 32-bit Glibc we have is time consuming enough.

c.

  reply	other threads:[~2003-01-15 18:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 18:14 [parisc-linux] 64 userspace FARINATI,LEANDRO (HP-Brazil,ex1)
2003-01-15 18:40 ` John David Anglin
2003-01-15 18:46   ` Matthew Wilcox
2003-01-15 18:54     ` Carlos O'Donell [this message]
2003-01-15 19:01   ` Carlos O'Donell
2003-01-15 19:09     ` John David Anglin
2003-01-15 19:26       ` Carlos O'Donell
2003-01-15 19:31       ` Carlos O'Donell
2003-01-15 19:49         ` John David Anglin
2003-01-15 19:17     ` John David Anglin
2003-01-15 19:27       ` Carlos O'Donell

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=20030115185438.GC19253@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=leandro.farinati@hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.