All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@lst.de>,
	darrick.wong@oracle.com, bfoster@redhat.com,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: use per-AG reservations for the finobt
Date: Fri, 27 Jan 2017 15:59:30 +0100	[thread overview]
Message-ID: <20170127145930.GA14983@lst.de> (raw)
In-Reply-To: <c4b1428d-6861-5290-d108-043ecbfeb1b1@sandeen.net>

On Thu, Jan 26, 2017 at 11:08:00PM -0600, Eric Sandeen wrote:
> This seems to cause regressions for me, at least on generic/108, xfs/004

xfs/004 isn't really broken, it just needs a change every time we
tune some reservations.   I've been pondering to just drop that
sub-check.

I can't run generic/108 as it requires a modular scsi_debug, and
none of my test setups uses modular kernels, so I'm curious on how
that could get broken by this change.

  reply	other threads:[~2017-01-27 15:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25  9:14 avoid running out of space during finobt insertation Christoph Hellwig
2017-01-25  9:14 ` [PATCH 1/2] xfs: only update mount/resv fields on success in __xfs_ag_resv_init Christoph Hellwig
2017-01-25  9:14 ` [PATCH 2/2] xfs: use per-AG reservations for the finobt Christoph Hellwig
2017-01-25 15:58   ` Darrick J. Wong
2017-01-27  5:08   ` Eric Sandeen
2017-01-27 14:59     ` Christoph Hellwig [this message]
2017-01-27 15:43       ` Eric Sandeen
2017-01-27 17:26         ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2017-01-24 20:16 avoid running out of space during finobt insertation Christoph Hellwig
2017-01-24 20:16 ` [PATCH 2/2] xfs: use per-AG reservations for the finobt Christoph Hellwig
2017-01-24 20:42   ` Darrick J. Wong
2017-01-25  9:13     ` Christoph Hellwig

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=20170127145930.GA14983@lst.de \
    --to=hch@lst.de \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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.