public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Skip Gaede <sgaede@attbi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory abuse with NFS Root filesystem?
Date: 23 Jun 2002 11:01:12 +0200	[thread overview]
Message-ID: <shs4rfuid2f.fsf@charged.uio.no> (raw)
In-Reply-To: <200206221648.36450.sgaede@attbi.com>

>>>>> " " == Skip Gaede <sgaede@attbi.com> writes:

     > Local boot: slabinfo after 30 minutes: size-2048 5 50 2048 3 25
     > 1

     > NFS Root: slabinfo after 15 & 60 minutes size-2048 187 228 2048
     > 94 114 1 (15 min) size-2048 918 928 2048 460 464 1 (60 min)

     > Anyone ever seen or heard of this before? Any thoughts on how
     > to isolate this to a root cause?

Have you tried combining the 'local boot' test with NFS?

AFAICS there are no memory leaks on NFS with x86 systems, but there
might be something wierd going on with other architectures.

Cheers,
   Trond

      reply	other threads:[~2002-06-23  9:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-22 20:48 Memory abuse with NFS Root filesystem? Skip Gaede
2002-06-23  9:01 ` Trond Myklebust [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=shs4rfuid2f.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgaede@attbi.com \
    /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