From: Aaron Lu <aaron.lu@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Rik van Riel <riel@redhat.com>,
David Rientjes <rientjes@google.com>,
Mel Gorman <mgorman@suse.de>, Minchan Kim <minchan@kernel.org>
Subject: Re: [RFC 0/3] reduce latency of direct async compaction
Date: Thu, 3 Dec 2015 17:25:25 +0800 [thread overview]
Message-ID: <20151203092525.GA20945@aaronlu.sh.intel.com> (raw)
In-Reply-To: <1449130247-8040-1-git-send-email-vbabka@suse.cz>
On Thu, Dec 03, 2015 at 09:10:44AM +0100, Vlastimil Babka wrote:
> Aaron, could you try this on your testcase?
The test result is placed at:
https://drive.google.com/file/d/0B49uX3igf4K4enBkdVFScXhFM0U
For some reason, the patches made the performace worse. The base tree is
today's Linus git 25364a9e54fb8296837061bf684b76d20eec01fb, and its
performace is about 1000MB/s. After applying this patch series, the
performace drops to 720MB/s.
Please let me know if you need more information, thanks.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Aaron Lu <aaron.lu@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Rik van Riel <riel@redhat.com>,
David Rientjes <rientjes@google.com>,
Mel Gorman <mgorman@suse.de>, Minchan Kim <minchan@kernel.org>
Subject: Re: [RFC 0/3] reduce latency of direct async compaction
Date: Thu, 3 Dec 2015 17:25:25 +0800 [thread overview]
Message-ID: <20151203092525.GA20945@aaronlu.sh.intel.com> (raw)
In-Reply-To: <1449130247-8040-1-git-send-email-vbabka@suse.cz>
On Thu, Dec 03, 2015 at 09:10:44AM +0100, Vlastimil Babka wrote:
> Aaron, could you try this on your testcase?
The test result is placed at:
https://drive.google.com/file/d/0B49uX3igf4K4enBkdVFScXhFM0U
For some reason, the patches made the performace worse. The base tree is
today's Linus git 25364a9e54fb8296837061bf684b76d20eec01fb, and its
performace is about 1000MB/s. After applying this patch series, the
performace drops to 720MB/s.
Please let me know if you need more information, thanks.
next prev parent reply other threads:[~2015-12-03 9:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 8:10 [RFC 0/3] reduce latency of direct async compaction Vlastimil Babka
2015-12-03 8:10 ` Vlastimil Babka
2015-12-03 8:10 ` [RFC 1/3] mm, compaction: reduce spurious pcplist drains Vlastimil Babka
2015-12-03 8:10 ` Vlastimil Babka
2015-12-03 8:10 ` [RFC 2/3] mm, compaction: make async direct compaction skip blocks where isolation fails Vlastimil Babka
2015-12-03 8:10 ` Vlastimil Babka
2015-12-03 8:10 ` [RFC 3/3] mm, compaction: direct freepage allocation for async direct compaction Vlastimil Babka
2015-12-03 8:10 ` Vlastimil Babka
2015-12-03 9:25 ` Aaron Lu [this message]
2015-12-03 9:25 ` [RFC 0/3] reduce latency of direct async compaction Aaron Lu
2015-12-03 9:38 ` Vlastimil Babka
2015-12-03 9:38 ` Vlastimil Babka
2015-12-03 11:35 ` Aaron Lu
2015-12-03 11:35 ` Aaron Lu
2015-12-03 11:52 ` Aaron Lu
2015-12-04 12:34 ` Vlastimil Babka
2015-12-04 12:34 ` Vlastimil Babka
2015-12-07 7:35 ` Joonsoo Kim
2015-12-07 7:35 ` Joonsoo Kim
2015-12-07 8:59 ` Aaron Lu
2015-12-08 0:41 ` Joonsoo Kim
2015-12-08 0:41 ` Joonsoo Kim
2015-12-08 5:14 ` Aaron Lu
2015-12-08 6:51 ` Joonsoo Kim
2015-12-08 6:51 ` Joonsoo Kim
2015-12-08 8:52 ` Aaron Lu
2015-12-08 8:52 ` Aaron Lu
2015-12-09 0:33 ` Joonsoo Kim
2015-12-09 0:33 ` Joonsoo Kim
2015-12-09 5:40 ` Aaron Lu
2015-12-09 5:40 ` Aaron Lu
2015-12-10 4:35 ` Joonsoo Kim
2015-12-10 4:35 ` Joonsoo Kim
2015-12-10 6:15 ` Aaron Lu
2015-12-10 6:15 ` Aaron Lu
2015-12-04 6:25 ` Aaron Lu
2015-12-04 6:25 ` Aaron Lu
2015-12-04 12:38 ` Vlastimil Babka
2015-12-04 12:38 ` Vlastimil Babka
2015-12-07 3:14 ` Aaron Lu
2015-12-07 3:14 ` Aaron Lu
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=20151203092525.GA20945@aaronlu.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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.