linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-xfs@vger.kernel.org,
	Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Subject: Re: xfs cgroup writeback support
Date: Wed, 26 Jun 2019 07:57:32 +0200	[thread overview]
Message-ID: <20190626055732.GA23631@lst.de> (raw)
In-Reply-To: <20190626055701.GA5171@magnolia>

On Tue, Jun 25, 2019 at 10:57:01PM -0700, Darrick J. Wong wrote:
> That may be, but I don't want to merge this patchset only to find out
> I've unleashed Pandora's box of untested cgroupwb hell... I /think/ they
> fixed all those problems, but it didn't take all that long tracing the
> blkg/blkcg object relationships for my brain to fall out. :/

c'mon.  We are adding handful of line patch to finally bring XFS in
line with everyone else.  That doesn't mean we want to take over
cgroup maintenance.

  reply	other threads:[~2019-06-26  5:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-24 13:43 xfs cgroup writeback support Christoph Hellwig
2019-06-24 13:43 ` [PATCH 1/2] xfs: simplify xfs_chain_bio Christoph Hellwig
2019-06-24 16:17   ` Darrick J. Wong
2019-06-25 10:00     ` Christoph Hellwig
2019-06-24 13:43 ` [PATCH 2/2] xfs: implement cgroup aware writeback Christoph Hellwig
2019-06-24 16:22   ` Darrick J. Wong
2019-06-25 10:00     ` Christoph Hellwig
2019-06-25 10:06       ` Stefan Priebe - Profihost AG
2019-06-25  3:25 ` xfs cgroup writeback support Darrick J. Wong
2019-06-25 10:05   ` Christoph Hellwig
2019-06-26  5:57     ` Darrick J. Wong
2019-06-26  5:57       ` Christoph Hellwig [this message]
2019-06-26 15:09         ` Darrick J. Wong

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=20190626055732.GA23631@lst.de \
    --to=hch@lst.de \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    /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).