linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: "Huang, Ying" <ying.huang@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Hugh Dickins <hughd@google.com>, Shaohua Li <shli@kernel.org>,
	Minchan Kim <minchan@kernel.org>
Subject: Re: [PATCH -mm -v3] mm, swap: Sort swap entries before free
Date: Fri, 07 Apr 2017 09:05:29 -0400	[thread overview]
Message-ID: <1491570329.8850.163.camel@redhat.com> (raw)
In-Reply-To: <20170407064901.25398-1-ying.huang@intel.com>

On Fri, 2017-04-07 at 14:49 +0800, Huang, Ying wrote:

> To solve the issue, the per-CPU buffer is sorted according to the
> swap
> device before freeing the swap entries.A A Test shows that the time
> spent by swapcache_free_entries() could be reduced after the patch.
> 
> Test the patch via measuring the run time of
> swap_cache_free_entries()
> during the exit phase of the applications use much swap space.A A The
> results shows that the average run time of swap_cache_free_entries()
> reduced about 20% after applying the patch.
> 
> Signed-off-by: Huang Ying <ying.huang@intel.com>
> Acked-by: Tim Chen <tim.c.chen@intel.com>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: Shaohua Li <shli@kernel.org>
> Cc: Minchan Kim <minchan@kernel.org>
> Cc: Rik van Riel <riel@redhat.com>

Acked-by: Rik van Riel <riel@redhat.com>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-04-07 13:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07  6:49 Huang, Ying
2017-04-07 13:05 ` Rik van Riel [this message]
2017-04-07 21:43 ` Andrew Morton
2017-04-11  7:03   ` Huang, Ying
2017-04-14  1:36   ` Huang, Ying
2017-04-14  1:41     ` Huang, Ying
2017-04-18  4:59 ` Minchan Kim
2017-04-19  8:14   ` Huang, Ying
2017-04-20  6:38     ` Minchan Kim
2017-04-20  7:15       ` Huang, Ying
2017-04-21 12:29         ` Huang, Ying
2017-04-21 23:29           ` Tim Chen
2017-04-23 13:16             ` Huang, Ying
2017-04-24 16:03               ` Tim Chen
2017-04-24  4:52           ` Minchan Kim
2017-04-24  6:47             ` Huang, Ying
2017-04-26 12:42             ` Huang, Ying
2017-04-26 20:13               ` Tim Chen
2017-04-27  1:21                 ` Huang, Ying
2017-04-27 16:48                   ` Tim Chen
2017-04-27  4:35               ` Minchan Kim
2017-04-28  1:09                 ` Huang, Ying
2017-04-28  7:42                   ` Minchan Kim
2017-04-28  8:05                     ` Huang, Ying
2017-04-28  9:00                       ` Minchan Kim
2017-04-28 11:48                         ` Huang, Ying
2017-04-28 13:35                           ` Huang, Ying
2017-05-02  5:02                             ` Minchan Kim
2017-05-02  5:35                               ` Huang, Ying
2017-05-02  5:48                                 ` Minchan Kim
2017-05-02  6:08                                   ` Huang, Ying

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=1491570329.8850.163.camel@redhat.com \
    --to=riel@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=shli@kernel.org \
    --cc=ying.huang@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