From: Mel Gorman <mgorman@suse.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Lsf-pc] [LSF/MM ATTEND] Other tracks I'm interested in (was Re: Persistent memory)
Date: Wed, 29 Jan 2014 10:16:31 +0000 [thread overview]
Message-ID: <20140129101631.GC6732@suse.de> (raw)
In-Reply-To: <CALCETrV2mtkKCMp6H+5gzoxi9kj9mx0GgsfiXqgn53AikCzFMw@mail.gmail.com>
On Tue, Jan 28, 2014 at 09:30:25AM -0800, Andy Lutomirski wrote:
> On Thu, Jan 16, 2014 at 4:56 PM, Andy Lutomirski <luto@amacapital.net> wrote:
> > I'm interested in a persistent memory track. There seems to be plenty
> > of other emails about this, but here's my take:
>
> I should add that I'm also interested in topics relating to the
> performance of mm and page cache under various abusive workloads.
> These include database-like things and large amounts of locked memory.
>
Out of curiousity, is there any data available on this against a recent
kernel? Locked memory should not cause the kernel to go to hell as the
pages should end up on the unevictable LRU list. If that is not happening,
it could be a bug. More details on the database configuration and test
case would also be welcome as it would help establish if the problem is
a large amount of memory being dirtied and then an fsync destroying the
world or something else.
--
Mel Gorman
SUSE Labs
--
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:[~2014-01-29 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:30 [LSF/MM ATTEND] Other tracks I'm interested in (was Re: Persistent memory) Andy Lutomirski
2014-01-29 10:16 ` Mel Gorman [this message]
2014-01-29 20:07 ` [Lsf-pc] " Andy Lutomirski
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=20140129101631.GC6732@suse.de \
--to=mgorman@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=luto@amacapital.net \
/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).