On Thu, 11 Jan 2001, Joseph Shraibman wrote:
> Scott Murray wrote:
> >
> > Nowadays the buffers are purely used for buffering access to the block
> > devices (e.g. disks). Pretty much everything else is now cached in the
> > page cache.
>
> That still doesn't answer my question. If everything i
Scott Murray wrote:
>
> On Wed, 10 Jan 2001, Joseph Shraibman wrote:
>
> > On a related note, what is the difference between "buffered" and
> > "cached" memory? I've noticed that with 2.4.0 there is barely any
> > buffered.
>
> Nowadays the buffers are purely used for buffering access to the b
On Wed, 10 Jan 2001, Joseph Shraibman wrote:
> On a related note, what is the difference between "buffered" and
> "cached" memory? I've noticed that with 2.4.0 there is barely any
> buffered.
Nowadays the buffers are purely used for buffering access to the block
devices (e.g. disks). Pretty mu
17:41
> To: scott murray; KIRKBRIDE Rob ([EMAIL PROTECTED])
> Cc: [EMAIL PROTECTED]
> Subject: Re: 2.4 kernel and threads
>
>
>
> On a related note, what is the difference between "buffered" and
> "cached" memory? I've noticed that with 2.4.0 there is b
On Thu, 4 Jan 2001, Joseph Shraibman wrote:
> >From README.linux to the 1.2.2 distrib:
> * If you get OutOfMemory errors when you try create more than xxx
> threads you'll have to increase the number of tasks supported by
> kernel (the default is 256 per user). Change NR_TASKS in
> /usr/src
>From README.linux to the 1.2.2 distrib:
* If you get OutOfMemory errors when you try create more than xxx
threads you'll have to increase the number of tasks supported by
kernel (the default is 256 per user). Change NR_TASKS in
/usr/src/linux/include/linux/tasks.h and recompile the kernel,
