Re: small improvement for mlock.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Yuri,

On Tue, Oct 26, 2010 at 9:14 AM, Yuri Kozlov <yuray@xxxxxxxxxxxx> wrote:
> Hello.
> """
> The VmLck field of the Linux-specific /proc/PID/status file shows how many
> kilobytes of memory the calling process has locked using mlock(),
> mlockall(), shmctl(2) SHM_LOCK, and mmap(2) MAP_LOCKED.
> """"
>
> Not for "calling process", but for process with PID?

Thanks. I applied:

@@ -288,7 +288,9 @@ The
 .I VmLck
 field of the Linux-specific
 .I /proc/PID/status
-file shows how many kilobytes of memory the calling process has locked using
+file shows how many kilobytes of memory the process with ID
+.I PID
+has locked using
 .BR mlock (),
 .BR mlockall (),
 .BR shmctl (2)

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux