public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Starr <shawn.starr@home.net>
To: Doug McNaught <doug@wireboard.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SHM Not working in 2.4.0-prerelease
Date: Wed, 03 Jan 2001 15:52:29 -0500	[thread overview]
Message-ID: <3A53910D.CAEDF4FF@home.net> (raw)
In-Reply-To: <3A537EA8.45889173@home.net> <m3g0j0l7e6.fsf@belphigor.mcnaught.org>

ahh ok, so everythings fine then. It would be nice though to see that
value perhaps in future they'll be a way.

Thanks,

Shawn.

Doug McNaught wrote:

> Shawn Starr <shawn.starr@home.net> writes:
>
> > [spstarr@coredump /etc]$ free
> >              total       used       free     shared    buffers
> > cached
> > Mem:         62496      61264       1232          0       1248
> > 28848
> >
> >
> > There's no shared memory being used?
>
> [...]
>
> > the shmfs is mounted. Is there any configuration i need to get shm
> > memory activiated?
>
> The 'shared' field in /proc/meminfo (source for 'top' and 'free') has
> nothing to do with {SysV,POSIX} shared memory.  The 'shared' field
> referred to memory that was used by more than one process (shared
> libraries, shared text segments etc).  As I understand it, under 2.4
> the 'shared' field is very expensive to calculate, so we don't--the
> zero value is there to avoid breaking programs that parse
> /proc/meminfo.
>
> -Doug

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2001-01-03 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 19:34 SHM Not working in 2.4.0-prerelease Shawn Starr
2001-01-03 20:15 ` Doug McNaught
2001-01-03 20:21   ` Albert D. Cahalan
2001-01-04 10:16     ` Christoph Rohland
2001-01-03 20:52   ` Shawn Starr [this message]

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=3A53910D.CAEDF4FF@home.net \
    --to=shawn.starr@home.net \
    --cc=doug@wireboard.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