lkml.org 
[lkml]   [2000]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Overcommitable memory??
Date
James Sutherland wrote:
>
> On 20 Mar 2000 15:19:23 -0800, you wrote:
>
> >In article <linux.kernel.fr1ddskpd1mnfr9gvjmnm8op9237gq61pd@4ax.com>,
> >James Sutherland <jas88@cam.ac.uk> wrote:
> >
> >>Unfortunately, this would break a lot of code which would depend on
> >>the current (perfectly reasonable) implementation of malloc() and
> >>stack space - namely, memory is only allocated when you use it.
> >
> > No, it wouldn't -- that code come pre-broken for your sysadminning
> > dispair.
>
> You are free to rewrite it all to fit your own replacement API if you
> like - that's the bit I'd try to avoid, though.

Umm, do you have any experience at all with computer programming?

I'm asking this because your arguments increasingly sound like
you've been living in a cave on the dark side of the moon for
the past 40 years, and now you're trying to get a handle on this
computer thing by reading back issues of WiReD and PC Computing.

____
david parsons \bi/ shudder.
\/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:57    [W:0.605 / U:0.732 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site