public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Allan Duncan <allan.d@bigpond.com>
To: Christoph Rohland <cr@sap.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>, linux-kernel@vger.kernel.org
Subject: Re: Shared memory quantity not being reflected by /proc/meminfo
Date: Sun, 24 Jun 2001 22:25:33 +1000	[thread overview]
Message-ID: <3B35DC3D.6D2DC9C@bigpond.com> (raw)
In-Reply-To: <200106240249.f5O2nIF07215@saturn.cs.uml.edu> <m3n16yjmkl.fsf@linux.local>

OK, it's fine by me if the "shared" under 2.2.x is not the same, however
in that case the field should not appear at all in meminfo, rather than
the current zero value, which leads lesser kernel hackers like me up the
garden path.

  reply	other threads:[~2001-06-24 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23 12:08 Shared memory quantity not being reflected by /proc/meminfo Allan Duncan
2001-06-24  2:49 ` Albert D. Cahalan
2001-06-24  8:44   ` Christoph Rohland
2001-06-24 12:25     ` Allan Duncan [this message]
2001-06-25  7:01       ` Christoph Rohland
2001-06-25 10:19         ` Allan Duncan

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=3B35DC3D.6D2DC9C@bigpond.com \
    --to=allan.d@bigpond.com \
    --cc=acahalan@cs.uml.edu \
    --cc=cr@sap.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