linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>,
	Sergei Trofimovich <slyfox@gentoo.org>
Subject: [PATCH v2 0/3] btrfs: don't spin in shrink_delalloc if there is nothing to free
Date: Fri, 20 May 2011 23:20:29 +0300	[thread overview]
Message-ID: <1305922832-22551-1-git-send-email-slyfox@gentoo.org> (raw)

The really interesting commit is
    btrfs: don't spin in shrink_delalloc if there is nothing to free
which fixes hogs on ENOSPC for me.


The rest of patches are cleanup.

Change since v2:
- Rebased against 2.6.39

Change since v1:
- Added Josef's Reviewed-by
- Fixed my MTA and patch numbering

Thanks!

P.S.:
It's also interesting to note, that 'shrink_delalloc' tries
to mess with 'bytes_reserved' (which are metadata reservation
right?)

The more I look at 'bytes_reserved' management paths the more I
think 'shrink_delalloc' should not touch them.

             reply	other threads:[~2011-05-20 20:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 20:20 Sergei Trofimovich [this message]
2011-05-20 20:20 ` [[PATCH v3] 1/3] btrfs: don't spin in shrink_delalloc if there is nothing to free Sergei Trofimovich
2011-05-20 20:20 ` [[PATCH v3] 2/3] btrfs: typo: 'btrfS' -> 'btrfs' Sergei Trofimovich
2011-05-20 20:20 ` [[PATCH v3] 3/3] btrfs: fix typo 'testeing' -> 'testing' Sergei Trofimovich
  -- strict thread matches above, loose matches on Subject: below --
2011-05-10 20:01 [PATCH v2 0/3] btrfs: don't spin in shrink_delalloc if there is nothing to free Sergei Trofimovich
2011-05-10 19:57 y
2011-05-10 19:57 y

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=1305922832-22551-1-git-send-email-slyfox@gentoo.org \
    --to=slyfox@gentoo.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).