public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Lord <lord@sgi.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Samuel Flory <sflory@rackable.com>,
	Austin Gonyou <austin@coremetrics.com>,
	Christian Guggenberger 
	<christian.guggenberger@physik.uni-regensburg.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-xfs@oss.sgi.com
Subject: Re: 2.4.20pre5aa2
Date: 14 Sep 2002 09:39:24 -0500	[thread overview]
Message-ID: <1032014367.1050.2.camel@laptop.americas.sgi.com> (raw)
In-Reply-To: <20020913211844.GP11605@dualathlon.random>

On Fri, 2002-09-13 at 16:18, Andrea Arcangeli wrote:

> So, returning to xfs, it is possible dbench really generates lots of
> simultaneous vmaps because of its concurrency, so I would suggest to add
> an atomic counter increased at every vmap/vmalloc and decreased at every
> vfree and to check it after every increase storing the max value in a
> sysctl, to see what's the max concurrency you reach with the vmaps. (you
> can also export the counter via the sysctl, to verify for no memleaks
> after unmounting xfs)
> 
> Andrea

There are no vmaps during normal operation on xfs unless you are
setting extended attributes of more than 4K in size, or you
used some more obscure mkfs options. Only filesystem recovery will
use it otherwise. 

Steve



  reply	other threads:[~2002-09-14 14:37 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 18:16 2.4.20pre5aa2 Christian Guggenberger
2002-09-11 18:24 ` 2.4.20pre5aa2 Austin Gonyou
2002-09-11 18:28   ` 2.4.20pre5aa2 Christian Guggenberger
     [not found]     ` <1031769317.24629.28.camel@UberGeek.coremetrics.com>
2002-09-11 18:45       ` 2.4.20pre5aa2 Christian Guggenberger
2002-09-11 18:51         ` 2.4.20pre5aa2 Austin Gonyou
2002-09-11 18:41   ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-12 23:29     ` 2.4.20pre5aa2 Samuel Flory
2002-09-12 23:45       ` 2.4.20pre5aa2 Stephen Lord
2002-09-13  0:06         ` 2.4.20pre5aa2 Samuel Flory
2002-09-13  0:23       ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13  0:47         ` 2.4.20pre5aa2 Stephen Lord
2002-09-13  0:54           ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13  2:14             ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 12:53               ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13 21:09                 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 21:18                   ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-14 14:39                     ` Stephen Lord [this message]
2002-09-15 11:13                       ` 2.4.20pre5aa2 Andi Kleen
2002-09-15 19:39                         ` 2.4.20pre5aa2 Samuel Flory
2002-09-16 16:03                 ` 2.4.20pre5aa2 Dave Hansen
2002-09-16 16:20                   ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-16 16:39                     ` 2.4.20pre5aa2 Dave Hansen
2002-09-13  1:27           ` 2.4.20pre5aa2 Samuel Flory
2002-09-13  2:14             ` 2.4.20pre5aa2 Samuel Flory
2002-09-13  1:18         ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 19:17           ` 2.4.20pre5aa2 Stephen Lord
2002-09-11 18:44 ` 2.4.20pre5aa2 Christoph Hellwig
2002-09-11 19:11   ` 2.4.20pre5aa2 Christian Guggenberger
  -- strict thread matches above, loose matches on Subject: below --
2002-09-09 16:50 2.4.20pre5aa2 Andrea Arcangeli
2002-09-10 18:51 ` 2.4.20pre5aa2 Joe Kellner

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=1032014367.1050.2.camel@laptop.americas.sgi.com \
    --to=lord@sgi.com \
    --cc=andrea@suse.de \
    --cc=austin@coremetrics.com \
    --cc=christian.guggenberger@physik.uni-regensburg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sflory@rackable.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