All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, xfs@oss.sgi.com
Subject: Re: [patch 2/2] xfs: use scalable vmap API
Date: Mon, 25 Jan 2010 19:33:09 +1100	[thread overview]
Message-ID: <20100125083309.GF19664@laptop> (raw)
In-Reply-To: <20100125081750.GA20012@infradead.org>

On Mon, Jan 25, 2010 at 03:17:50AM -0500, Christoph Hellwig wrote:
> On Mon, Jan 25, 2010 at 06:54:45PM +1100, Nick Piggin wrote:
> > Is this on a 32-bit system with small vmalloc area?
> 
> Yes.

OK, I would say it could easily be just due to fragmentation then.


> > When the vmap allocation fails, it would be good to basically see the
> > alloc_map and dirty_map for each of the vmap_blocks. This is going to be
> > a lot of information. Basically for all blocks with
> > free+dirty == VMAP_BBMAP_BITS are ones that could be released and you
> > could try the alloc again.
> 
> Any easy way to get them?  Sorry, not uptodate on your new vmalloc
> implementation anymore.

Let me try writing a few (tested) patches here first that I can send you.


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com, linux-mm@kvack.org
Subject: Re: [patch 2/2] xfs: use scalable vmap API
Date: Mon, 25 Jan 2010 19:33:09 +1100	[thread overview]
Message-ID: <20100125083309.GF19664@laptop> (raw)
In-Reply-To: <20100125081750.GA20012@infradead.org>

On Mon, Jan 25, 2010 at 03:17:50AM -0500, Christoph Hellwig wrote:
> On Mon, Jan 25, 2010 at 06:54:45PM +1100, Nick Piggin wrote:
> > Is this on a 32-bit system with small vmalloc area?
> 
> Yes.

OK, I would say it could easily be just due to fragmentation then.


> > When the vmap allocation fails, it would be good to basically see the
> > alloc_map and dirty_map for each of the vmap_blocks. This is going to be
> > a lot of information. Basically for all blocks with
> > free+dirty == VMAP_BBMAP_BITS are ones that could be released and you
> > could try the alloc again.
> 
> Any easy way to get them?  Sorry, not uptodate on your new vmalloc
> implementation anymore.

Let me try writing a few (tested) patches here first that I can send you.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-01-25  8:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21  8:25 [patch 1/2] xfs: remove old vmap cache Nick Piggin
2008-10-21  8:27 ` [patch 2/2] xfs: use scalable vmap API Nick Piggin
2008-10-21 12:09   ` Christoph Hellwig
2008-10-22  9:30     ` Nick Piggin
2010-01-19 12:15       ` Christoph Hellwig
2010-01-19 12:15         ` Christoph Hellwig
2010-01-25  7:54         ` Nick Piggin
2010-01-25  7:54           ` Nick Piggin
2010-01-25  8:17           ` Christoph Hellwig
2010-01-25  8:17             ` Christoph Hellwig
2010-01-25  8:33             ` Nick Piggin [this message]
2010-01-25  8:33               ` Nick Piggin
2010-01-25 12:37               ` Nick Piggin
2010-01-25 12:37                 ` Nick Piggin
2010-01-25 12:39                 ` Christoph Hellwig
2010-01-25 12:39                   ` Christoph Hellwig
2010-01-25 21:34                 ` Christoph Hellwig
2010-01-25 21:34                   ` Christoph Hellwig
2010-01-27  8:38                   ` Nick Piggin
2010-01-27  8:38                     ` Nick Piggin
2010-02-01 11:01                     ` Christoph Hellwig
2010-02-01 11:01                       ` Christoph Hellwig
2010-02-01 11:28                       ` Nick Piggin
2010-02-01 11:28                         ` Nick Piggin
2010-01-25  8:30           ` Nick Piggin
2010-01-25  8:30             ` Nick Piggin
2008-10-21 12:09 ` [patch 1/2] xfs: remove old vmap cache Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2010-03-16 18:55 [PATCH 2/2] xfs: use scalable vmap API Alex Elder

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=20100125083309.GF19664@laptop \
    --to=npiggin@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.