From: "zhaoyifan (H)" <zhaoyifan28@huawei.com>
To: wangzijie <wangzijie1@honor.com>, <hsiangkao@linux.alibaba.com>
Cc: <bintian.wang@honor.com>, <feng.han@honor.com>,
<linux-erofs@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<stopire@gmail.com>, <xiang@kernel.org>
Subject: Re: [PATCH] erofs-utils: avoid redundant memcpy and sha256() for dedupe
Date: Fri, 15 Aug 2025 17:58:33 +0800 [thread overview]
Message-ID: <16d9e356-d0b0-4f62-9d92-9b696d7ffb4b@huawei.com> (raw)
In-Reply-To: <20250815095449.4163442-1-wangzijie1@honor.com>
Hi Zijie,
It would be quite appreciated if you could help us polish the
multithreading -Ededupe implementation. I will try to rebase the
existing code to the latest codebase ASAP.
You could find the design decision in multithreading -Ededupe in this paper:
https://dl.acm.org/doi/pdf/10.1145/3671016.3671395
Thanks,
Yifan
On 2025/8/15 17:54, wangzijie wrote:
>> Hi Zijie,
>>
>> On 2025/8/15 16:44, wangzijie wrote:
>>> We have already use xxh64() for filtering first for dedupe, when we
>>> need to skip the same xxh64 hash, no need to do memcpy and sha256(),
>>> relocate the code to avoid it.
>>>
>>> Signed-off-by: wangzijie <wangzijie1@honor.com>
>> Thanks for the patch, it makes sense to me since we only keep one
>> record according to xxh64 (instead of sha256) for now:
>>
>> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com>
>>
>> Although I think multi-threaded deduplication is more useful, see:
>> https://github.com/erofs/erofs-utils/issues/25
>> but I'm not sure if you're interested in it... ;-)
> Hi Xiang,
> Thank you for providing this information, I want to optimize mkfs time with
> dedupe option and send this patch. I will find time to research Yifan's demo
> of multi-threaded deduplication and try to provide some help.
>
>> Thanks,
>> Gao Xiang
>
>
prev parent reply other threads:[~2025-08-15 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 8:44 wangzijie
2025-08-15 9:04 ` Gao Xiang
2025-08-15 9:54 ` wangzijie
2025-08-15 9:58 ` zhaoyifan (H) [this message]
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=16d9e356-d0b0-4f62-9d92-9b696d7ffb4b@huawei.com \
--to=zhaoyifan28@huawei.com \
--cc=bintian.wang@honor.com \
--cc=feng.han@honor.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stopire@gmail.com \
--cc=wangzijie1@honor.com \
--cc=xiang@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
all inboxes | Powered by JetHome®