All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charan Teja Kalla <charante@codeaurora.org>
To: akpm@linux-foundation.org, 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
Cc: 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: Sat, 3 Jul 2021 15:52:10 +0530	[thread overview]
Message-ID: <c0150787-5f85-29ac-9666-05fabedabb1e@codeaurora.org> (raw)
In-Reply-To: <cover.1624028025.git.charante@codeaurora.org>

A gentle ping to have your valuable comments.

Thanks,
Charan

On 6/18/2021 8:48 PM, Charan Teja Reddy wrote:
> These patches support triggering of proactive compaction by user on write
> to the /proc/sys/vm/compaction_proactiveness.
> 
> Changes in V4:
>   -- Changed the code as the 'proactive_defer' counter is removed.
>   -- No changes in the logic of triggering the proactive compaction.
>   -- Removed the 'proactive_defer' counter.
> 
> Changes in V3:
>   -- Fixed review comments from Vlastimil and others.
>   -- Fixed wake up logic when compaction_proactiveness is zero.
>   -- https://lore.kernel.org/patchwork/patch/1438211/
> 
> Changes in V2:
>   -- remove /proc/../proactive_compact_memory interface trigger for proactive compaction
>   -- Intention is same that add a way to trigger proactive compaction by user.
>   -- https://lore.kernel.org/patchwork/patch/1431283/
> 
> Changes in V1:
>   -- Created the new /proc/sys/vm/proactive_compact_memory in
>      interface to trigger proactive compaction from user 
>   -- https://lore.kernel.org/lkml/1619098678-8501-1-git-send-email-charante@codeaurora.org/
> 
> 
> Charan Teja Reddy (3):
>   mm: compaction:  optimize proactive compaction deferrals
>   mm: compaction: support triggering of proactive compaction by user
>   mm: compaction: fix wakeup logic of proactive compaction
> 
>  Documentation/admin-guide/sysctl/vm.rst |  3 +-
>  include/linux/compaction.h              |  2 ++
>  include/linux/mmzone.h                  |  1 +
>  kernel/sysctl.c                         |  2 +-
>  mm/compaction.c                         | 61 +++++++++++++++++++++++++++------
>  5 files changed, 56 insertions(+), 13 deletions(-)
> 

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum, a Linux Foundation Collaborative Project

  parent reply	other threads:[~2021-07-03 10:22 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 ` Charan Teja Kalla [this message]
2021-07-16  4:27   ` [PATCH V4,0/3] mm: compaction: proactive compaction trigger by user Andrew Morton
2021-07-16 10:44     ` Charan Teja Kalla

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=c0150787-5f85-29ac-9666-05fabedabb1e@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.