public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: ioremap()/PCI sickness in 2.4.18-rc2 (FIXED ALMOST)
Date: Wed, 20 Feb 2002 16:35:52 -0700	[thread overview]
Message-ID: <20020220163552.B1730@vger.timpanogas.org> (raw)
In-Reply-To: <20020220152011.A1252@vger.timpanogas.org> <E16dfoX-00050r-00@the-village.bc.nu>
In-Reply-To: <E16dfoX-00050r-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 20, 2002 at 11:06:17PM +0000

On Wed, Feb 20, 2002 at 11:06:17PM +0000, Alan Cox wrote:
> > Sigh .... I am only using 2 GB on a 4GB capable processor (actually 
> > a 64 GB capable processor).  Looks like a patch is needed.  Who is 
> > maintaining vmalloc.c at present so I know who to submit a patch 
> > to?
> 
> Actually you are using a 64Gb capable processor that is only capable of 
> sanely addressing 4Gb at a time, total across both user and kernel space
> and takes a hefty hit whenever you switch which 4Gb you are peering at.
> 
> If you want to make sensible use of even 4Gb user/4Gb kernel you need to
> take a page table reload at syscall time and deal with quite messy handling
> for copy to/from user. 
> 
> [If someone from Intel disagrees please do so publically - I'd love to have
>  someone prove the limit can be dealt with 8)]


I'll get to work on it.  The 4 bit PTE extention to enable 48 bit
addresses is quite ugly, and I agree -- heavy.  There may. however, 
be no other way to make this work properly.  The SCI address space is 
explicitly addressable, so it may be possible to enable this on 
the PCI-SCI adapters **ONLY** (not ccNuma) without getting into
general user/kernel copy issues since the SCI address space is 
typically assumed in this model to be an explicit entity for most
apps.   :-)

Jeff

Jeff




> -
> 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:[~2002-02-20 23:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 17:33 ioremap()/PCI sickness in 2.4.18-rc2 Jeff V. Merkey
2002-02-20 17:35 ` Jeff V. Merkey
2002-02-20 17:26   ` Jeff Garzik
2002-02-20 17:30     ` David S. Miller
2002-02-20 18:00       ` Jeff V. Merkey
2002-02-20 21:54         ` ioremap()/PCI sickness in 2.4.18-rc2 (FIXED ALMOST) Jeff V. Merkey
2002-02-20 21:51           ` Jeff Garzik
2002-02-20 22:20             ` Jeff V. Merkey
2002-02-20 22:53               ` Jeff V. Merkey
2002-02-20 23:06               ` Alan Cox
2002-02-20 23:35                 ` Jeff V. Merkey [this message]
     [not found]                 ` <mailman.1014247349.21244.linux-kernel2news@redhat.com>
2002-02-20 23:44                   ` Pete Zaitcev
2002-02-20 22:10           ` Jeff V. Merkey
2002-02-20 22:08             ` arjan
2002-02-22 11:08             ` Steffen Persvold
2002-02-22 18:17               ` Jeff V. Merkey
2002-02-22 18:42                 ` David Mosberger
2002-02-22 18:51                   ` Jeff Garzik
2002-02-22 19:01                     ` David Mosberger
2002-02-22 19:42                   ` Jeff V. Merkey
2002-02-23  2:22               ` Richard Henderson
2002-02-20 18:44       ` ioremap()/PCI sickness in 2.4.18-rc2 Steffen Persvold
2002-02-20 20:36         ` Jeff V. Merkey
2002-02-22 11:49           ` Steffen Persvold
2002-02-22 18:21             ` Jeff V. Merkey
2002-02-20 17:46     ` Jeff V. Merkey

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=20020220163552.B1730@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@mandrakesoft.com \
    --cc=jmerkey@timpanogas.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