From: Peng Zhang <zhangpeng.00@bytedance.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Liam.Howlett@oracle.com, corbet@lwn.net,
akpm@linux-foundation.org, brauner@kernel.org, surenb@google.com,
michael.christie@oracle.com, mjguzik@gmail.com,
mathieu.desnoyers@efficios.com, npiggin@gmail.com,
peterz@infradead.org, oliver.sang@intel.com, mst@redhat.com,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Peng Zhang <zhangpeng.00@bytedance.com>
Subject: Re: [PATCH v6 03/10] maple_tree: Introduce interfaces __mt_dup() and mtree_dup()
Date: Wed, 25 Oct 2023 17:19:54 +0800 [thread overview]
Message-ID: <bf7d4005-d32c-42d9-a748-a7c421130be6@bytedance.com> (raw)
In-Reply-To: <ZTfw1nw15wijNnCB@casper.infradead.org>
在 2023/10/25 00:29, Matthew Wilcox 写道:
> On Tue, Oct 24, 2023 at 04:32:51PM +0800, Peng Zhang wrote:
>> +++ b/lib/maple_tree.c
>> @@ -4,6 +4,10 @@
>> * Copyright (c) 2018-2022 Oracle Corporation
>> * Authors: Liam R. Howlett <Liam.Howlett@oracle.com>
>> * Matthew Wilcox <willy@infradead.org>
>> + *
>> + * Implementation of algorithm for duplicating Maple Tree
>
> I thought you agreed that line made no sense, and you were just going to
> drop it? just add your copyright, right under ours.
I'm sorry, I misunderstood your meaning last time. I will make
corrections in the next version. Are you saying that only the
following two lines are needed? This still needs to be confirmed
with Liam.
>
>> + * Copyright (c) 2023 ByteDance
>> + * Author: Peng Zhang <zhangpeng.00@bytedance.com>
>
next prev parent reply other threads:[~2023-10-25 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 8:32 [PATCH v6 00/10] Introduce __mt_dup() to improve the performance of fork() Peng Zhang
2023-10-24 8:32 ` [PATCH v6 01/10] maple_tree: Add mt_free_one() and mt_attr() helpers Peng Zhang
2023-10-24 8:32 ` [PATCH v6 02/10] maple_tree: Introduce {mtree,mas}_lock_nested() Peng Zhang
2023-10-24 8:32 ` [PATCH v6 03/10] maple_tree: Introduce interfaces __mt_dup() and mtree_dup() Peng Zhang
2023-10-24 16:29 ` Matthew Wilcox
2023-10-25 9:19 ` Peng Zhang [this message]
2023-10-25 16:28 ` Liam R. Howlett
2023-10-24 8:32 ` [PATCH v6 04/10] radix tree test suite: Align kmem_cache_alloc_bulk() with kernel behavior Peng Zhang
2023-10-24 8:32 ` [PATCH v6 05/10] maple_tree: Add test for mtree_dup() Peng Zhang
2023-10-24 8:32 ` [PATCH v6 06/10] maple_tree: Update the documentation of maple tree Peng Zhang
2023-10-24 8:32 ` [PATCH v6 07/10] maple_tree: Skip other tests when BENCH is enabled Peng Zhang
2023-10-24 8:32 ` [PATCH v6 08/10] maple_tree: Update check_forking() and bench_forking() Peng Zhang
2023-10-24 8:32 ` [PATCH v6 09/10] maple_tree: Preserve the tree attributes when destroying maple tree Peng Zhang
2023-10-24 8:32 ` [PATCH v6 10/10] fork: Use __mt_dup() to duplicate maple tree in dup_mmap() Peng Zhang
2023-10-26 18:18 ` [PATCH v6 00/10] Introduce __mt_dup() to improve the performance of fork() Liam R. Howlett
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=bf7d4005-d32c-42d9-a748-a7c421130be6@bytedance.com \
--to=zhangpeng.00@bytedance.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=michael.christie@oracle.com \
--cc=mjguzik@gmail.com \
--cc=mst@redhat.com \
--cc=npiggin@gmail.com \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=surenb@google.com \
--cc=willy@infradead.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