public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eastham, M. Thomas (Anitel Technologies)" <EasthaMT@bp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Greater than 2TB Filesystem support?
Date: Wed, 11 Sep 2002 14:18:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701906020@msgid-missing> (raw)

Is there anyone out there that can give me an indication of when the 2TB FS
limitation will be addressed?  We are ready to implement XFS based IDE Raid
IA64 servers with 4+TB today.  Any information you can provide me about
timelines would be very helpful.

Regards,
Thomas Eastham

-----Original Message-----
From: Keith Owens [mailto:kaos@sgi.com]
Sent: Wednesday, September 11, 2002 12:51 AM
To: Steven Cole
Cc: linux-ia64@linuxia64.org
Subject: Re: [Linux-ia64] [trivial] Request for merging of two sets of
redundant SGI IA64Configure.help texts


Steven Cole <elenstev@mesatop.com> wrote:
>Could one of you help resolve the following very trivial problem.  In
>2.4.20-pre5 Documentation/Configure.help, there exists two
>Configure.help entries for CONFIG_IA64_SGI_SN_SIM and
>CONFIG_IA64_SGI_SN_DEBUG.
>
>The configurators will of course only display the first of the two.
>Would someone please indicate which of the texts is the more accurate or
>combine them as you see fit.  You can send me the results or make up a
>patch yourself.
>
>If this is a moot point, deleting the second text would be the default
>thing to do.

The first set is wrong.  There is also an error in ia64/config.in for
one of these variables.  Patch against 2.4.19.

--- Documentation/Configure.help.orig	Wed Sep 11 15:44:36 2002
+++ Documentation/Configure.help	Wed Sep 11 15:45:24 2002
@@ -24409,16 +24409,6 @@
 
   If you don't know what to do, choose "generic".
 
-CONFIG_IA64_SGI_SN_SIM
-  Build a kernel that runs on both the SGI simulator AND on hardware.
-  There is a very slight performance penalty on hardware for including this
-  option.
-
-CONFIG_IA64_SGI_SN_DEBUG
-  This enables addition debug code that helps isolate
-  platform/kernel bugs. There is a small but measurable performance
-  degradation when this option is enabled.
-
 # Choice: pagesize
 Kernel page size
 CONFIG_IA64_PAGE_SIZE_4KB
--- arch/ia64/config.in.orig	Wed Sep 11 15:45:29 2002
+++ arch/ia64/config.in	Wed Sep 11 15:49:01 2002
@@ -75,7 +75,7 @@
 
 if [ "$CONFIG_IA64_SGI_SN1" = "y" ] || [ "$CONFIG_IA64_SGI_SN2" = "y" ];
then
 	define_bool CONFIG_IA64_SGI_SN y
-	bool '  Enable extra debugging code' CONFIG_IA64_SGI_SN_DEBUG n
+	bool '  Enable extra debugging code' CONFIG_IA64_SGI_SN_DEBUG
 	bool '  Enable SGI Medusa Simulator Support' CONFIG_IA64_SGI_SN_SIM
 	bool '  Enable autotest (llsc). Option to run cache test instead of
booting' \
 			CONFIG_IA64_SGI_AUTOTEST n


_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64


             reply	other threads:[~2002-09-11 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 14:18 Eastham, M. Thomas (Anitel Technologies) [this message]
2002-09-11 18:03 ` [Linux-ia64] Greater than 2TB Filesystem support? David Mosberger
2002-09-12  0:41 ` Peter Chubb
2002-09-12 19:20 ` Eastham, M. Thomas (Anitel Technologies)

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-105590701906020@msgid-missing \
    --to=easthamt@bp.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