From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-mm@kvack.org, linux-s390@vger.kernel.org,
Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Jan Kara <jack@suse.cz>,
Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Subject: Re: [PATCH] software dirty bits for s390
Date: Tue, 5 Feb 2013 11:28:21 -0800 [thread overview]
Message-ID: <20130205112821.0e35b241@mschwide> (raw)
In-Reply-To: <1360087925-8456-2-git-send-email-schwidefsky@de.ibm.com>
On Tue, 5 Feb 2013 10:12:04 -0800
Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
> Greetings,
>
> good news, I got performance results for a selected set of workloads
> with my software dirty bit patch (thanks Christian!). We found no
> downsides to the software dirty bits, and a substantial improvement
> in CPU utilization for the FIO test with mostly read mappings.
>
> The patch can now go upstream.
Grumpf, 0000-cover-letter.patch~ in the outgoing directory.
Please ignore.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
--
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>
next prev parent reply other threads:[~2013-02-05 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 18:12 [PATCH] software dirty bits for s390 Martin Schwidefsky
2013-02-05 18:12 ` Martin Schwidefsky
2013-02-05 19:28 ` Martin Schwidefsky [this message]
2013-02-05 18:12 ` [PATCH] s390/mm: implement software dirty bits Martin Schwidefsky
2013-02-06 11:21 ` Mel Gorman
2013-02-06 18:16 ` Martin Schwidefsky
2013-02-07 0:20 ` Hugh Dickins
2013-02-07 19:18 ` Martin Schwidefsky
2013-02-11 14:27 ` Martin Schwidefsky
2013-02-11 22:08 ` Hugh Dickins
2013-02-12 8:46 ` Martin Schwidefsky
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=20130205112821.0e35b241@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mgorman@suse.de \
/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).