From: "Huang, Rulin" <rulin.huang@intel.com>
To: Baoquan He <bhe@redhat.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
akpm@linux-foundation.org, colin.king@intel.com,
hch@infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lstoakes@gmail.com, tianyou.li@intel.com,
tim.c.chen@intel.com, wangyang.guo@intel.com,
zhiguo.zhou@intel.com, rulin.huang@intel.com
Subject: Re: [PATCH v7 1/2] mm/vmalloc: Moved macros with no functional change happened
Date: Thu, 7 Mar 2024 13:48:52 +0800 [thread overview]
Message-ID: <654d9312-85df-4f57-8151-1ad802d5201e@intel.com> (raw)
In-Reply-To: <Zek1ZVmCtddF7f3y@MiWiFi-R3L-srv>
Thanks for your guiding and encouragement!
On 2024/3/7 11:32, Baoquan He wrote:
> On 03/07/24 at 11:01am, Huang, Rulin wrote:
>> We have made changes based on your latest suggestions.
>> 1.Removed bugs_on.
>> 2.Removed adjustion of macros.
>>
>> We submitted patch v8 based on this. Thanks to Baoquan for the
>> discussion, and could you please help to review and confirm if there are
>> any problems on the latest version?
>
> Looks good to me, I don't want to exhaust a newcomer's enthusiasm and
> patience before you get used to this :-). Will ack, thanks for the
> awesome work.
>
next prev parent reply other threads:[~2024-03-07 5:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 15:54 [PATCH v7 0/2] mm/vmalloc: lock contention optimization under multi-threading rulinhuang
2024-03-01 15:54 ` [PATCH v7 1/2] mm/vmalloc: Moved macros with no functional change happened rulinhuang
2024-03-06 13:23 ` Baoquan He
2024-03-06 19:01 ` Uladzislau Rezki
2024-03-07 1:23 ` Baoquan He
2024-03-07 3:01 ` Huang, Rulin
2024-03-07 3:32 ` Baoquan He
2024-03-07 5:48 ` Huang, Rulin [this message]
2024-03-07 19:53 ` Uladzislau Rezki
2024-03-07 19:16 ` Uladzislau Rezki
2024-03-08 8:23 ` Baoquan He
2024-03-08 10:28 ` Uladzislau Rezki
2024-03-09 4:54 ` Baoquan He
2024-03-01 15:54 ` [PATCH v7 2/2] mm/vmalloc: Eliminated the lock contention from twice to once rulinhuang
2024-03-06 13:55 ` Baoquan He
2024-03-06 9:18 ` [PATCH v7 0/2] mm/vmalloc: lock contention optimization under multi-threading Huang, Rulin
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=654d9312-85df-4f57-8151-1ad802d5201e@intel.com \
--to=rulin.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=colin.king@intel.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=tianyou.li@intel.com \
--cc=tim.c.chen@intel.com \
--cc=urezki@gmail.com \
--cc=wangyang.guo@intel.com \
--cc=zhiguo.zhou@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).