From: Martin Zwickel <martin.zwickel@technotrend.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB)
Date: Wed, 3 Dec 2003 16:15:05 +0100 [thread overview]
Message-ID: <20031203161505.475f1bad.martin.zwickel@technotrend.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
Hi there,
I have a small question:
If I look into the "/proc/<xserver pid>/status" file, there is a VmLck with a
4TeraByte number.
Is that normal?
# cat /proc/7850/status
Name: X
State: S (sleeping)
SleepAVG: 101%
Tgid: 7850
Pid: 7850
PPid: 7848
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmSize: 377396 kB
VmLck: 4294967292 kB
VmRSS: 65724 kB
VmData: 101456 kB
VmStk: 320 kB
VmExe: 1604 kB
VmLib: 6844 kB
Threads: 1
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 8000000000301000
SigCgt: 00000000518066cb
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
Most other processes have 0kb.
cat /proc/*/status | grep VmLck
...
VmLck: 0 kB
VmLck: 0 kB
VmLck: 2060 kB
VmLck: 0 kB
VmLck: 0 kB
VmLck: 4 kB
VmLck: 0 kB
...
Regards,
Martin
ps.:
I'm using the nvidia driver.
# cat /proc/driver/nvidia/version
NVRM version: NVIDIA Linux x86 nvidia.o Kernel Module 1.0-4496 Wed Jul 16
19:03:09 PDT 2003 GCC version: gcc version 3.2.3 20030422 (Gentoo Linux 1.4
3.2.3-r2, propolice)
# cat /proc/version
Linux version 2.6.0-test11 (root@phoebee) (gcc version 3.2.3 20030422 (Gentoo
Linux 1.4 3.2.3-r2, propolice)) #6 Thu Nov 27 13:02:23 CET 2003
--
MyExcuse:
SCSI's too wide.
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-12-03 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 15:15 Martin Zwickel [this message]
2003-12-03 15:28 ` Måns Rullgård
2003-12-03 15:46 ` 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=20031203161505.475f1bad.martin.zwickel@technotrend.de \
--to=martin.zwickel@technotrend.de \
--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®