Re: [PATCH 19/25] vfs: implement opportunistic short dedupe

Subject: Re: [PATCH 19/25] vfs: implement opportunistic short dedupe
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sun, 14 Oct 2018 10:26:04 -0700
Cc: david@xxxxxxxxxxxxx, sandeen@xxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, linux-cifs@xxxxxxxxxxxxxxx, Amir Goldstein <amir73il@xxxxxxxxx>, linux-unionfs@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, ocfs2-devel@xxxxxxxxxxxxxx
In-reply-to: <153938927786.8361.10345203650384514542.stgit@magnolia>
References: <153938912912.8361.13446310416406388958.stgit@magnolia> <153938927786.8361.10345203650384514542.stgit@magnolia>
User-agent: Mutt/1.9.2 (2017-12-15)

How is RFR_SHORT_DEDUPE so different from RFR_SAME_DATA + RFR_CAN_SHORTEN
that we need another flag for it?

References:
- [PATCH v4 00/25] fs: fixes for serious clone/dedupe problems
  - From: Darrick J. Wong
- [PATCH 19/25] vfs: implement opportunistic short dedupe
  - From: Darrick J. Wong