From: Charan Teja Kalla <charante@codeaurora.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: vbabka@suse.cz, corbet@lwn.net, mcgrof@kernel.org,
keescook@chromium.org, yzaikin@google.com, osalvador@suse.de,
rientjes@google.com, mchehab+huawei@kernel.org,
lokeshgidra@google.com, andrew.a.klychkov@gmail.com,
xi.fengfei@h3c.com, nigupta@nvidia.com,
dave.hansen@linux.intel.com, famzheng@amazon.com,
mateusznosek0@gmail.com, oleksandr@redhat.com, sh_def@163.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
"vinmenon@codeaurora.org" <vinmenon@codeaurora.org>
Subject: Re: [PATCH V4,0/3] mm: compaction: proactive compaction trigger by user
Date: Fri, 16 Jul 2021 16:14:01 +0530 [thread overview]
Message-ID: <f24af677-1005-b14c-4bbe-f41feefe172b@codeaurora.org> (raw)
In-Reply-To: <20210715212744.1a43012c21711bafd25e5b68@linux-foundation.org>
Thanks Andrew for the reply!!
On 7/16/2021 9:57 AM, Andrew Morton wrote:
> On Sat, 3 Jul 2021 15:52:10 +0530 Charan Teja Kalla <charante@codeaurora.org> wrote:
>
>> A gentle ping to have your valuable comments.
>
> Can we please have a resend?
>
> The series has two fixes against the current code. Please separate
> that work out from the new feature. So a 2-patch series to fix the bugs
> followed by a single patch to add your new feature.
https://lore.kernel.org/patchwork/patch/1448789/ -- Can go as a separate
bug fix.
https://lore.kernel.org/patchwork/patch/1448793/ -- is the second bug
fix which is tightly coupled with the feature of explicitly waking of
kcompactd on the event of change in compaction proactiveness, when it is
sleeping with MAX_SCHEDULE_TIMEOUT.
So, will make the changes with 1 patch bug fix and 2nd patch feature
where the second bug fix also clubbed.
I hope this is fine.
>
>
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation Collaborative Project
prev parent reply other threads:[~2021-07-16 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 15:18 [PATCH V4,0/3] mm: compaction: proactive compaction trigger by user Charan Teja Reddy
2021-06-18 15:18 ` [PATCH V4 1/3] mm: compaction: optimize proactive compaction deferrals Charan Teja Reddy
2021-06-18 15:18 ` [PATCH V4 2/3] mm: compaction: support triggering of proactive compaction by user Charan Teja Reddy
2021-06-18 15:18 ` [PATCH V4 3/3] mm: compaction: fix wakeup logic of proactive compaction Charan Teja Reddy
2021-07-03 10:22 ` [PATCH V4,0/3] mm: compaction: proactive compaction trigger by user Charan Teja Kalla
2021-07-16 4:27 ` Andrew Morton
2021-07-16 10:44 ` Charan Teja Kalla [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=f24af677-1005-b14c-4bbe-f41feefe172b@codeaurora.org \
--to=charante@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.a.klychkov@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=famzheng@amazon.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=mateusznosek0@gmail.com \
--cc=mcgrof@kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nigupta@nvidia.com \
--cc=oleksandr@redhat.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=sh_def@163.com \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.org \
--cc=xi.fengfei@h3c.com \
--cc=yzaikin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.