public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.5.45 with CONFIG_NUMA=y
Date: Wed, 04 Dec 2002 01:11:46 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805500@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805486@msgid-missing>

On Wed, Nov 27, 2002 at 05:22:04PM +0100, Xavier Bru wrote:
>  > > . Current settings for DIG are : 512MB/bank, 16GB/node,(mmzone.h)  but our
>  > > platform can support 64 GB/node (Even with less memory, bios maps
>  > > each node memory modulo 64GB). 
>  > > As it has been cleanly coded :-), we just changed DIG_BANKSHIFT to 31 
>  > > (2GB banks) and system runs. 
>  > > Should these values bee incremented in the future ?
>  > 
>  > Maybe that should be an option for the kernel configuration system?
> 
> This should be OK for us.

Wanna come up with a patch? :)  It could just be something like 'MB per
bank' or somesuch, only visible when DIG and DISCONTIG are turned on.

> Seems that we use the VGA mode through /dev/mem (No driver is actually 
> loaded). 
> Are there some known problems with /dev/mem and DISCONTIG_MEM ? 

I don't think there are discontig mem issues really, but platform issues
possibly.  On our platform for example, X might go looking in /dev/mem
for a list of PCI cards and then use the info in the PCI config space
incorrectly (e.g. IRQ values).  Other platforms probably have this issue
too, not sure about yours though.

> Do you think we should have more chances validating Frame buffer support and the
> card driver ? (I think platform has no AGP support).

Possibly.  I know that some of the frame buffer drivers were written to
expect the card to be uninitialized so that they'll work on non-x86
platforms.

Jesse


      parent reply	other threads:[~2002-12-04  1:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26 17:54 [Linux-ia64] 2.5.45 with CONFIG_NUMA=y Xavier Bru
2002-11-26 18:33 ` Jesse Barnes
2002-11-27 16:22 ` Xavier Bru
2002-12-04  1:11 ` Jesse Barnes [this message]

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=marc-linux-ia64-105590709805500@msgid-missing \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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