Linux-Development-Sys Digest #720, Volume #8 Tue, 15 May 01 17:13:13 EDT
Contents:
Re: malloc returns NULL! ([EMAIL PROTECTED])
Why O_SYNC and fsync are slow on Linux? ("Heikki Tuuri")
Re: transpareny ("Darren LS")
Re: looking for a sed tip (Chris Cox)
Kernel 2.4.4 and Adaptec 1480 Slim SCSI Desperate HELP Please. David Hinds?
("E-mu")
Will Linux recognize >4GB RAM on Pentium-III Xeon? (Doug Chan)
Re: SIGSEGV is not blocking ("Michael J. Saletnik")
Re: kernel timer: microsecond ?? ("Norm Dresner")
Re: module programming / input question ("Norm Dresner")
Re: Why O_SYNC and fsync are slow on Linux? (Dragan Cvetkovic)
Re: SIGSEGV is not blocking (David Schwartz)
Re: shutdown kernel code ("Norm Dresner")
Re: Will Linux recognize >4GB RAM on Pentium-III Xeon? (reader of news)
Sync and Async disk I/Os (Zhiyong Xu)
Re: Why is RedHat 7.1 so fast? (At150bogomips)
Re: SIGSEGV is not blocking
Re: Will Linux recognize >4GB RAM on Pentium-III Xeon? (Doug Chan)
Can I use aio_read() for UDP sockets? ("Roger Tragin")
Free OS ?
Re: Free OS ? (Jim Cochrane)
Re: Free OS ? (Grant Edwards)
Re: Free OS ? ([EMAIL PROTECTED])
Re: Will Linux recognize >4GB RAM on Pentium-III Xeon? (Johan Kullstam)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: malloc returns NULL!
Date: 15 May 2001 15:23:32 GMT
On Tue, 15 May 2001 12:43:53 +0100 Karl Heyes <[EMAIL PROTECTED]>
wrote:
| In article <[EMAIL PROTECTED]>, "Wolfram Gloger"
| <[EMAIL PROTECTED]> wrote:
|> "Karl Heyes" <[EMAIL PROTECTED]> writes:
|>> Allocating 10 bytes a time using the standard malloc is very wasteful,
|>> typically (If I remember my data structures classes) about 6 pointers get
|>> used for each allocation, ie 24 bytes, as well the actual space requested
|>> and any alignment.
|> In glibc-2, space for two pointers is used in every allocation, plus the
|> size field and alignment: the minimum chunk size is `only' 16 bytes.
|> malloc()ing 10 bytes therefore `wastes' 6 bytes. Regards,
|> Wolfram.
|
| I don't know what the implementation of glibc malloc is like but if two
| pointers are used and 10 bytes requested then that a minimum of 18 bytes
| for each allocation (not counting alignment, size field and chunk usage).
|
| Surely you must see at least a 1:2 ratio in this case.
Running this little program tells a lot. It told me that malloc for my
version of glibc (2.1.3) needs 4 bytes, and the ratio for wanting 10 bytes
to be allocated approached 1:1.6. For the case of 70 million records this
would require 1120000000 bytes, well into 1G, but not yet close to 2G.
=============================================================================
#include <stdlib.h>
#include <stdio.h>
int main ( int argc, char **argv )
{
double ratio ;
char * prev_ptr ;
char * this_ptr ;
char * hi_ptr ;
char * lo_ptr ;
long delta ;
size_t total ;
size_t usage ;
if ( argc <= 1 ) {
fprintf( stderr, "How many bytes per allocation?\n" );
return 1;
}
prev_ptr = NULL;
total = 0;
usage = strtoul( argv[1], NULL, 0 );
for (;;) {
this_ptr = malloc( usage );
if ( ! this_ptr ) break;
total += usage;
if ( prev_ptr ) {
if ( hi_ptr < this_ptr ) hi_ptr = this_ptr;
if ( lo_ptr > this_ptr ) lo_ptr = this_ptr;
delta = ( (long) prev_ptr ) - ( (long) this_ptr );
if ( delta < 0 ) delta = -delta;
ratio = ( (double) ( hi_ptr - lo_ptr ) ) / ( (double) total );
printf( "%08lx delta=%2ld total=%8Zu hi=%08lx lo=%08lx
ratio=%10.7f\n",
(unsigned long) this_ptr, delta, total,
(unsigned long) hi_ptr, (unsigned long) lo_ptr, ratio );
} else {
hi_ptr = this_ptr;
lo_ptr = this_ptr;
printf( "%08lx (first allocation)\n", (unsigned long) this_ptr );
}
prev_ptr = this_ptr;
}
printf( "done: out of memory\n" );
return 0;
}
=============================================================================
--
=================================================================
| Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ |
| [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ |
=================================================================
------------------------------
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
Subject: Why O_SYNC and fsync are slow on Linux?
Date: Tue, 15 May 2001 18:22:39 GMT
Hi!
Does anyone happen to know who is responsible for the file cache and disk
management in Linux?
On different systems I have measured strange differences in performance
depending
on whether I open a file with O_SYNC and let the operating system do the
flushing
of the file to disk after each write, or if I open without O_SYNC, and call
fsync myself.
Some observations:
On Red Hat 6.2 and 7.? Intel big block writes are very slow if I open the
file with O_SYNC.
I call pwrite to write 1 MB chunks to the file, and I get only 1 MB/s write
speed.
If I open without O_SYNC and call fsync only after writing the whole 100 MB
file,
I get 5 MB/s.
On a Linux-Compaq Alpha I measured the following: if I open with O_SYNC, I
can flush
the end of my file (it is a log file) to disk 170 times / second. If I do
not open with O_SYNC,
but call fsync or fdatasync after each write, I get only 50 writes/second.
On the Red Hat 7.? I get 500 writes per second if I open with O_SYNC. That
is too much
because the disk does not rotate 500 rotations/second. Does the disk fool
the operating
sytem to believe a write has ended while it has not?
On Windows NT I have not noticed such performance problems if I use
non-buffered
i/o to a file.
I have written a database engine InnoDB under MySQL and bumped into these
problems
on Linux.
Regards,
Heikki Tuuri
Innobase Oy
http://www.innobase.fi
------------------------------
From: "Darren LS" <[EMAIL PROTECTED]>
Crossposted-To:
alt.linux,comp.os.linux.development.apps,linux.redhat.devel,linux.redhat.development
Subject: Re: transpareny
Date: Tue, 15 May 2001 19:33:48 +0100
<[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]...
> In article <dBDL6.3906$[EMAIL PROTECTED]>,
> Darren LS <[EMAIL PROTECTED]> wrote:
>
> >how would I incorporate this in my programme? would it be the first part
of
> >the main function or would I have to stick mymain code in a function?
>
> I suggest looking at the source of a couple of daemons to see
> how they do it.
>
> --
> http://www.spinics.net/linux
thanks. Any site that open with blue penguins gets my vote
------------------------------
From: Chris Cox <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.development
Subject: Re: looking for a sed tip
Date: Tue, 15 May 2001 18:53:00 GMT
Argh... what a cross post...
You could use " instead..
sed -e "s/x/'/g"
Of course you will get a round of eval on
the string that you might not want depending
on what x is.
If your example is simple as you have stated...
you may want to consider "tr" instead.
tr 'x' '\140'
tr is good for character for character substitutions.
Regards,
Chris
Winston Smith wrote:
>
> Hi,
>
> I'm trying to make a shell script that use sed to replace in a text
> stream some characters with the ' char but if I use
> sed -e 's/x/'/g' I get an error because the first ' end the expression.
> So I'm looking for a special notation like \' or something.
>
> Thank you in advance.
------------------------------
From: "E-mu" <[EMAIL PROTECTED]>
Subject: Kernel 2.4.4 and Adaptec 1480 Slim SCSI Desperate HELP Please. David Hinds?
Date: 15 May 2001 18:57:08 GMT
I was told by Alan Cox that the driver for the apa_1480 Adaptec Slim Scsi
was intentionally left out because the new driver for aic7xxx in this kernel
2.4.4 will handle the aha_1480 cardbus card.
Well, I am having problems when the kernel boots up. Here is what I can get
from it thus far.
Here is the error I get during the boot up of the kernel. Maybe you can
tell me what to do?
QoutPOS = 210
ahc_pci:2:0:0: Warning no command for scb0 (cmdcmptl)
QoutPOS = 211
ahc_pci:2:0:0: Warning no command for scb0 (cmdcmptl)
QoutPOS = 212
ahc_pci:2:0:0: Warning no command for scb0 (cmdcmptl)
QoutPOS = 213
ahc_pci:2:0:0: Warning no command for scb0 (cmdcmptl)
etc etc
This loops about 100 or more times
Then this happens:
QOUTPOS = -1
ahc_pci:2:0:0 Someone reset channel A
Unable to handle Kernel NULL pointer dereference at virtual address 00000000
printing eip:
c02727f6
*pde=00000000
Oops:0000
Cpu: 0010:[<c02727f6>]
Eflags: 0001000096
eax: 00000041
etc etc etc followed by a STACK DUMP, which I could not copy all that
information down!
Then this happens:
Kernel Panic : Aiee, Killing interrupt handler!
In interrupt handler-not syncing
Can you halep me on this or point me to someone who can help me figure out
what is the deal here?
I was told by Alan Cox that I may have to make some changes in my PCMCIA
config file BUT, the config file is not bring accessed at this point during
the Kernel Boot phase. Or at least I think its not?
My kernel is completly monolithic except the Firewire driver. Previous
kernels had the aha_1480 driver in SCSI section under PCMCIA. There was a
choice for it specifically and it could only be chosen as module. This
allways worked fine for me, until they removed it from kernel 2.4.4, since
it suppose to be handled by the new aic7xxx diver tree. I wonder about that
though?
Thanks for you patience :):)
------------------------------
Crossposted-To: comp.os.linux.hardware
From: [EMAIL PROTECTED] (Doug Chan)
Subject: Will Linux recognize >4GB RAM on Pentium-III Xeon?
Date: Tue, 15 May 2001 18:57:36 GMT
I know that the Pentium-III Xeon supports 36-bit addression (up to 64Gb)
of RAM however it required that the OS knows about this "pse-36" mode
for this extended memory support.
Does Linux support this extended memory mode?
Thanks,
-Doug
apollo at world.std.com
------------------------------
Crossposted-To: comp.os.linux.development.apps,comp.programming.threads
Subject: Re: SIGSEGV is not blocking
From: "Michael J. Saletnik" <[EMAIL PROTECTED]>
Date: Tue, 15 May 2001 19:30:06 GMT
"Arthur H. Gold" <[EMAIL PROTECTED]> writes:
> First of all, once you've entered the "land of undefined behavior"
I agree; however I'm bothered about what POSIX says. The Linux man
page says:
According to POSIX, the behaviour of a process is undefined after
it ignores a SIGFPE, SIGILL, or SIGSEGV signal that was not
generated by the kill() or the raise() functions.
Now, setting a signal's disposition to SIG_IGN is not the same as
blocking it. When blocked, it's still pending.
So although we're doing something kinda strange here, by theory and
documentation I agree that it ought to work, and am curious why it
doesn't.
--
{michael}
------------------------------
From: "Norm Dresner" <[EMAIL PROTECTED]>
Subject: Re: kernel timer: microsecond ??
Date: Tue, 15 May 2001 19:42:21 GMT
NortonNg <[EMAIL PROTECTED]> wrote in message
news:9dpgqn$122c$[EMAIL PROTECTED]...
> hi all,
>
> i would like to set a timer in kernel space for doing something.
> however, i wonder if i can set a 50us(microsecond) timer, after it
expired,
> i would like to do something.
> I have read the code in /usr/src/linux/net/sched/sch_tbf.c . it use
> timer_list structure and call add_timer() to set a timer. but i suppose
the
> timer is ms(millisecond), isn't it?
>
> the code is something like that:
>
> struct timer_list wd_timer; /* Watchdog timer */
> int delay;
> ...
> delay=1;
>
> del_timer(&wd_timer);
> wd_timer.expires = jiffies + delay;
> add_timer(&wd_timer);
>
> ///////////
> jiffies is 10ms, i suppose. How can i set a timer with 50us??
>
>
> Regards,
If you're willing to make a small change to your OS, you can do exactly what
you want. The Real-Time extensions to Linux allow creating exact (to the
microsecond) task wake-ups and a whole lot more. While I haven't done
extensive testing, I've never found anything in normal Linux that wasn't
compatible with RTL.
http://www.rtlinux.org
is the place to start.
Norm
------------------------------
From: "Norm Dresner" <[EMAIL PROTECTED]>
Subject: Re: module programming / input question
Date: Tue, 15 May 2001 19:47:51 GMT
Abhijit Bose <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hello,
> I would like to have a user process dump some data structure into a file
> in /proc (or some other
> directory) and have a kernel module read the contents of the file. I
> would then use this data
> in one of the functions in /net directory (ip_output.c) to change
> contents of an
> outgoing packet.
Ugh. The best (and only safe) ways to have a user-program communicate
information to a module is:
1. Create a new minor-device number and let the user-program open it and
do normal write() operations.
2. Use standard ioctl() to pass to the module the address of a buffer in
user-space where the information is located.
> My question is:
> will the data be available to the entire kernel if I export the symbols
> corresponding to these
> data variables from the module after it reads the data from the file in
> /proc ? e.g. I can define a structure in the module and have this
> structure as well as the actual variable (object) exported.
> I plan to use
> get_user in asm/uaccess.h - is this recommended for 2.2.x - 2.4.x
At least in 2.2.x, copy_from_user() and copy_to_user() work just fine.
> kernels ? Thanks very much,
> Abhijit Bose
Norm
------------------------------
Subject: Re: Why O_SYNC and fsync are slow on Linux?
From: Dragan Cvetkovic <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Date: 15 May 2001 15:49:53 -0400
"Heikki Tuuri" <[EMAIL PROTECTED]> writes:
> On the Red Hat 7.? I get 500 writes per second if I open with O_SYNC. That
> is too much
> because the disk does not rotate 500 rotations/second. Does the disk fool
> the operating
> sytem to believe a write has ended while it has not?
Well, on Solaris 8 (my favourite source of man files), there is a note in
the man page for fsync(3C):
The manner in which the data reach the physical medium
depends on both implementation and hardware. The fsync()
function returns when notified by the device driver that the
write has taken place.
So it seems it very much depend on the disk hardware. I don't know if that
helps though. I prefer to use fdatasync().
Bye, Dragan
--
Dragan Cvetkovic,
To be or not to be is true. G. Boole
------------------------------
From: David Schwartz <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.programming.threads
Subject: Re: SIGSEGV is not blocking
Date: Tue, 15 May 2001 12:48:53 -0700
"Michael J. Saletnik" wrote:
> So although we're doing something kinda strange here, by theory and
> documentation I agree that it ought to work, and am curious why it
> doesn't.
You say it ought to "work". What do you mean? What behavior would
constitute working? You have left no reasonable thing for the
implementation to do.
DS
------------------------------
From: "Norm Dresner" <[EMAIL PROTECTED]>
Subject: Re: shutdown kernel code
Date: Tue, 15 May 2001 19:52:06 GMT
Zhiyong Xu <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi,
> I want to know where's the code related to shutdown process in
> kernel, when you submit command shutdown or reboot. Could you please
> tell the source file name?
>
> Thanks in advance.
If you execute
:
find . -name '*.c' | xargs grep reboot
somewhere near the top of the kernel source-code tree, you'll find
several good examples of how to do that. Also, the source for the
watchdog-timer drivers contains exactly that.
Norm
------------------------------
From: [EMAIL PROTECTED] (reader of news)
Crossposted-To: comp.os.linux.hardware
Subject: Re: Will Linux recognize >4GB RAM on Pentium-III Xeon?
Reply-To: [EMAIL PROTECTED]
Date: Tue, 15 May 2001 19:57:14 GMT
2.4 kernel can handle up to 64gb.
just have to turn it on during compilation.
don't know whether it will for your xeon
On Tue, 15 May 2001 18:57:36 GMT, Doug Chan <[EMAIL PROTECTED]> wrote:
>I know that the Pentium-III Xeon supports 36-bit addression (up to 64Gb)
>of RAM however it required that the OS knows about this "pse-36" mode
>for this extended memory support.
>Does Linux support this extended memory mode?
>
>Thanks,
>-Doug
>apollo at world.std.com
------------------------------
From: Zhiyong Xu <[EMAIL PROTECTED]>
Subject: Sync and Async disk I/Os
Date: Tue, 15 May 2001 16:00:49 -0400
Hi,
In linux, is modification of metadata sync write, data block
async write? Is there any possibility once it is async write, and change
to sync wtite during the normal activity?
Thanks!
------------------------------
From: [EMAIL PROTECTED] (At150bogomips)
Date: 15 May 2001 20:06:30 GMT
Subject: Re: Why is RedHat 7.1 so fast?
'jtnews' <[EMAIL PROTECTED]> wrote:
>I'm getting 5MB/sec dump transfer rates
>across an NFS filesystem with RedHat 7.1
>where I used to get only about 1.5MB/sec.
My guess would be that hdparam was used (by default) to tune the hard drives.
(Yes, one can get such huge improvements from changing the disk prefetch
blocking and other parameters. On older Red Hat's this was not done (not
having 7.1--only 7.0--I do not know if Red Hat changed this), presumably
because it can cause some problems with older drives.)
Paul A. Clayton
------------------------------
From: [EMAIL PROTECTED] ()
Crossposted-To: comp.os.linux.development.apps,comp.programming.threads
Subject: Re: SIGSEGV is not blocking
Date: Tue, 15 May 2001 20:07:08 -0000
In article <[EMAIL PROTECTED]>,
Michael J. Saletnik <[EMAIL PROTECTED]> wrote:
>Now, setting a signal's disposition to SIG_IGN is not the same as
>blocking it. When blocked, it's still pending.
>
>So although we're doing something kinda strange here, by theory and
>documentation I agree that it ought to work, and am curious why it
>doesn't.
Where is your program going to go after a seg fault? That's why the
results are undefined.
--
http://www.spinics.net/linux
------------------------------
Crossposted-To: comp.os.linux.hardware
From: [EMAIL PROTECTED] (Doug Chan)
Subject: Re: Will Linux recognize >4GB RAM on Pentium-III Xeon?
Date: Tue, 15 May 2001 20:19:02 GMT
Thanks!
I read somewhere that the process address space is still limited to
less than 4GB?
-Doug
In article <[EMAIL PROTECTED]>,
reader of news <[EMAIL PROTECTED]> wrote:
>2.4 kernel can handle up to 64gb.
>just have to turn it on during compilation.
>don't know whether it will for your xeon
>
>On Tue, 15 May 2001 18:57:36 GMT, Doug Chan <[EMAIL PROTECTED]> wrote:
>>I know that the Pentium-III Xeon supports 36-bit addression (up to 64Gb)
>>of RAM however it required that the OS knows about this "pse-36" mode
>>for this extended memory support.
>>Does Linux support this extended memory mode?
>>
>>Thanks,
>>-Doug
>>apollo at world.std.com
------------------------------
From: "Roger Tragin" <[EMAIL PROTECTED]>
Subject: Can I use aio_read() for UDP sockets?
Date: Tue, 15 May 2001 16:22:59 -0400
Hi,
Under Windoze I am using WSARecvFrom() to read datagrams from a UDP socket
asynchronously. Is there an equivalent under Linux?
I did try using aio_read() but it failed.
Thanks
Roger
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Free OS ?
Date: Tue, 15 May 2001 20:30:10 -0000
This sounds like a silly question, but if Linux is an Open-Source OS, where
can you get it for free? Also what are Distributors and how are Developers
like Red Hat and Caldera able to charge for Linux? From what I have been
reading that is not what Linus Trevold had in mind when he developed Linux.
Im new to any Operating System that is not MS Windows and would really
like to learn and install Linux. Any suggestions would be appreciated.
Thanks, STG94
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: [EMAIL PROTECTED] (Jim Cochrane)
Subject: Re: Free OS ?
Date: 15 May 2001 14:42:48 -0600
Finding a linux distribution that can be downloaded for free is
straightforward (although it will take a long time if you have a slow
connection) - simply go to one of the distributors sites and search for a
link to download their ditro - shouldn't be hard to find. Or try a search
on google.com, such as:
download linux distribution
(google is often very good for these things, if you can figure out the
right combination of search words.)
I'll leave the other questions to others.
In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
>
>This sounds like a silly question, but if Linux is an Open-Source OS, where
>can you get it for free? Also what are Distributors and how are Developers
>like Red Hat and Caldera able to charge for Linux? From what I have been
>reading that is not what Linus Trevold had in mind when he developed Linux.
>Im new to any Operating System that is not MS Windows and would really
>like to learn and install Linux. Any suggestions would be appreciated.
> Thanks, STG94
>
>--
>Posted via CNET Help.com
>http://www.help.com/
--
Jim Cochrane
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Subject: Re: Free OS ?
Date: Tue, 15 May 2001 20:45:44 GMT
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
>This sounds like a silly question, but if Linux is an Open-Source OS, where
>can you get it for free?
http://www.linux.org/dist/index.html
www.linuxiso.org
www.redhat.com
www.debian.org
>Also what are Distributors
People who gather up stuff, burn it onto CD's and sell or
give-away the CDs.
>and how are Developers like Red Hat and Caldera able to charge
>for Linux?
Becaus people are willing pay them.
>From what I have been reading that is not what Linus Trevold
>had in mind when he developed Linux.
I can't speak for what Linus had in mind, but:
1) Linus only developed a small (albiet critical) part of
what RedHat et al put on CDs.
2) Linus released it under the GPL, which explicitly gives
people like RedHat permission to do what they do.
>Im new to any Operating System that is not MS Windows and would really
>like to learn and install Linux. Any suggestions would be appreciated.
www.linux.org
--
Grant Edwards grante Yow! By MEER biz doo
at SCHOIN...
visi.com
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Free OS ?
Date: Tue, 15 May 2001 20:50:11 GMT
<[EMAIL PROTECTED]> writes:
> This sounds like a silly question, but if Linux is an Open-Source
> OS, where can you get it for free? Also what are Distributors and
> how are Developers like Red Hat and Caldera able to charge for
> Linux? From what I have been reading that is not what Linus Trevold
> had in mind when he developed Linux. Im new to any Operating System
> that is not MS Windows and would really like to learn and install
> Linux. Any suggestions would be appreciated.
Take a look at <http://www.kernel.org/> to get it "for free."
Caldera and RHAT are not, as such "charging for Linux;" they are
charging for _distributing_ it.
Those that are interested in getting the code freely have little
trouble doing so [modulo needing to pay for ISP connections and the
likes].
--
(concatenate 'string "aa454" "@freenet.carleton.ca")
http://www.ntlug.org/~cbbrowne/resume.html
"Well, it's assembly language, you know. You don't want to have too much
taste..." -- Dave Moon
------------------------------
Crossposted-To: comp.os.linux.hardware
Subject: Re: Will Linux recognize >4GB RAM on Pentium-III Xeon?
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 15 May 2001 17:07:20 -0400
[EMAIL PROTECTED] (Doug Chan) writes:
> Thanks!
> I read somewhere that the process address space is still limited to
> less than 4GB?
yes. i believe this is true for ia32 processors such as the p-3 xeon.
what is the situation for 64 bit processors such as ultrasparc or
alpha? these might have larger limits on memory usage.
you seem willing to part with large coin since you are considering the
intel wallet vaccuum -- maybe equipment from, e.g., sun would be
competitive in price/performance?
> -Doug
>
> In article <[EMAIL PROTECTED]>,
> reader of news <[EMAIL PROTECTED]> wrote:
> >2.4 kernel can handle up to 64gb.
> >just have to turn it on during compilation.
> >don't know whether it will for your xeon
> >
> >On Tue, 15 May 2001 18:57:36 GMT, Doug Chan <[EMAIL PROTECTED]> wrote:
> >>I know that the Pentium-III Xeon supports 36-bit addression (up to 64Gb)
> >>of RAM however it required that the OS knows about this "pse-36" mode
> >>for this extended memory support.
> >>Does Linux support this extended memory mode?
> >>
> >>Thanks,
> >>-Doug
> >>apollo at world.std.com
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
sysengr
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to the
comp.os.linux.development.system newsgroup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
