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: [PATCH 2/2] xfs: implement cgroup aware writeback
Date: Tue, 25 Jun 2019 12:00:57 +0200 [thread overview]
Message-ID: <20190625100057.GD1462@lst.de> (raw)
In-Reply-To: <20190624162215.GS5387@magnolia>
On Mon, Jun 24, 2019 at 09:22:15AM -0700, Darrick J. Wong wrote:
> On Mon, Jun 24, 2019 at 03:43:15PM +0200, Christoph Hellwig wrote:
> > Link every newly allocated writeback bio to cgroup pointed to by the
> > writeback control structure, and charge every byte written back to it.
> >
> > Tested-by: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
>
> Was this tested by running shared/011? Or did it involve other checks?
I verified it with shared/011 and local frobbing. Stefan can chime
in on what testing he did.
next prev parent reply other threads:[~2019-06-25 10:01 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 [this message]
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
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=20190625100057.GD1462@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 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.