linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB)
Date: Wed, 03 Dec 2003 16:28:25 +0100	[thread overview]
Message-ID: <yw1x8yltudie.fsf@kth.se> (raw)
In-Reply-To: 20031203161505.475f1bad.martin.zwickel@technotrend.de

Martin Zwickel <martin.zwickel@technotrend.de> writes:

> 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?
>
> VmLck:  4294967292 kB

FWIW, that is -4 as an unsigned 32-bit number.

> Most other processes have 0kb.

My X shows 0.  I have a SiS chip.

-- 
Måns Rullgård
mru@kth.se


  reply	other threads:[~2003-12-03 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 15:15 2.6.0-t11 /proc/<xserver pid>/status question (VmLck > 4TB) Martin Zwickel
2003-12-03 15:28 ` Måns Rullgård [this message]
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=yw1x8yltudie.fsf@kth.se \
    --to=mru@kth.se \
    --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;
as well as URLs for NNTP newsgroup(s).