mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Deas, Jim" <James.Deas@warnerbros.com>
To: linux-kernel@vger.kernel.org
Subject: Re: vmalloc - kmalloc and page locks
Date: Tue, 22 Jul 2003 06:57:26 -0700	[thread overview]
Message-ID: <S270278AbTGVNmc/20030722134232Z+5616@vger.kernel.org> (raw)

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)



             reply	other threads:[~2003-07-22 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 13:57 Deas, Jim [this message]
2003-07-22 15:38 ` Antonio Vargas
  -- strict thread matches above, loose matches on Subject: below --
2003-07-22 13:00 Deas, Jim
2003-07-22 13:07 ` Gábor Lénárt
2003-07-22 13:12   ` Gábor Lénárt
2003-07-22 13:07 ` William Lee Irwin III

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=S270278AbTGVNmc/20030722134232Z+5616@vger.kernel.org \
    --to=james.deas@warnerbros.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®