content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: vmalloc - kmalloc and page locks
Date: Tue, 22 Jul 2003 06:57:26 -0700
Thread-Topic: vmalloc - kmalloc and page locks
Thread-Index: AcNQUwJnnRJsjabgQYG66psKzZAgPgABVf8g
From: "Deas, Jim" <James.Deas@warnerbros.com>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain;
 charset=iso-8859-2
Content-Transfer-Encoding: 8BIT
Message-Id: <S270278AbTGVNmc/20030722134232Z+5616@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2286
Lines: 59

Thanks for the clarification. I am using mlockall on the user application. This 
still leaves me with the mystery of why my system usage goes from 3% to
50% randomly while playing data streams off the harddrive. I can also make
system usage stay at 50% by opening a third stream.
These streams are pulling data at 1.5MB/s each from different files (same HD).
I don't see that as a big strain on the hardware (4.5MB/s total data rate).
Where else should I look to find the bottleneck/latency issue?

Regards,
J. Deas


-----Original Message-----
From: G?bor L?n?rt [mailto:lgb@lgb.hu]
Sent: Tuesday, July 22, 2003 6:13 AM
To: Deas, Jim
Cc: linux-kernel@vger.kernel.org
Subject: Re: vmalloc - kmalloc and page locks


Errrrr ... Sorry, I did not read your mail carefully ;-(
I meant in case of a user process you can use mlock() and such :)
AFAIK the kernel itself is not pagable ...

On Tue, Jul 22, 2003 at 03:07:18PM +0200, G?bor L?n?rt wrote:
> Please read something about the mlock() and/or mlockall() functions.
> The prototype can be found in [/usr/include/]sys/mman.h
> You can read there:
> 
> /* Guarantee all whole pages mapped by the range [ADDR,ADDR+LEN) to
>    be memory resident.  */
> extern int mlock (__const void *__addr, size_t __len) __THROW;
> [...]
> /* Cause all currently mapped pages of the process to be memory resident
>    until unlocked by a call to the `munlockall', until the process exits,
>    or until the process calls `execve'.  */
> extern int mlockall (int __flags) __THROW;
> 
> On Tue, Jul 22, 2003 at 06:00:14AM -0700, Deas, Jim wrote:
> > How can I look at what memory are being paged out of memory in the kernel
> > or how to lock kmalloc and vmalloc pages so they do not get put to swap?
> [...]
> 
> - G?bor (larta'H)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
- G?bor (larta'H)


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