From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christian Theune <ct@flyingcircus.io>, linux-xfs@vger.kernel.org
Subject: Re: Reading about CoW architecture / Performance Limits
Date: Wed, 11 Jan 2017 01:10:11 -0800 [thread overview]
Message-ID: <20170111091011.GA29454@infradead.org> (raw)
In-Reply-To: <20170111080544.GB5883@birch.djwong.org>
On Wed, Jan 11, 2017 at 12:05:44AM -0800, Darrick J. Wong wrote:
> > 3. There appears to be code that allows retroactively creating CoW for
> > two files that existed separately before. Is that (planned to be)
> > exposed to userland?
>
> No plans for that at the moment. There used to be a debugging knob, but
> it was ripped out before upstreaming the code.
I think he's asking for the dedup ioctl, which is supported.
next prev parent reply other threads:[~2017-01-11 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 7:07 Reading about CoW architecture / Performance Limits Christian Theune
2017-01-10 7:45 ` Darrick J. Wong
[not found] ` <C97BB12C-3C30-493B-BE9A-9E8C7CB5D1A4@flyingcircus.io>
2017-01-11 7:59 ` Darrick J. Wong
[not found] ` <9713E613-6953-4AD3-89B1-C0EF639E771C@flyingcircus.io>
2017-01-11 8:05 ` Darrick J. Wong
2017-01-11 9:10 ` Christoph Hellwig [this message]
2017-01-11 17:52 ` 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=20170111091011.GA29454@infradead.org \
--to=hch@infradead.org \
--cc=ct@flyingcircus.io \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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