From: Mark Goodwin <markgw@sgi.com>
To: lachlan@sgi.com
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] Increase the default size of the reserved blocks pool
Date: Tue, 30 Sep 2008 13:26:17 +1000 [thread overview]
Message-ID: <48E19C59.7090303@sgi.com> (raw)
In-Reply-To: <48E097B5.3010906@sgi.com>
Lachlan McIlroy wrote:
> The current default size of the reserved blocks pool is easy to deplete
> with certain workloads, in particular workloads that do lots of concurrent
> delayed allocation extent conversions. If enough transactions are running
> in parallel and the entire pool is consumed then subsequent calls to
> xfs_trans_reserve() will fail with ENOSPC. Also add a rate limited
> warning so we know if this starts happening again.
>
Should we also change the semantics of the XFS_SET_RESBLKS ioctl
so that the passed in value is the minimum required by the caller,
i.e. silently succeed if the current value is more than that?
Cheers
-- Mark
next prev parent reply other threads:[~2008-09-30 3:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 8:54 [PATCH] Increase the default size of the reserved blocks pool Lachlan McIlroy
2008-09-30 3:26 ` Mark Goodwin [this message]
2008-09-30 4:25 ` Dave Chinner
2008-09-30 6:08 ` Lachlan McIlroy
2008-09-30 6:37 ` Dave Chinner
2008-09-30 4:11 ` Dave Chinner
2008-09-30 4:29 ` Dave Chinner
2008-09-30 6:19 ` Lachlan McIlroy
2008-09-30 6:40 ` Dave Chinner
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=48E19C59.7090303@sgi.com \
--to=markgw@sgi.com \
--cc=lachlan@sgi.com \
--cc=xfs-dev@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox