From: Jan Kara <jack@suse.cz>
To: Michel Lespinasse <walken@google.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [Lsf-pc] [ATTEND] LSF/MM conference
Date: Mon, 6 Feb 2012 11:30:24 +0100 [thread overview]
Message-ID: <20120206103024.GA6890@quack.suse.cz> (raw)
In-Reply-To: <CANN689EAfiTdXSr8L+UTWxJLEGHeLVziNLCsdbLuqzsVdERexg@mail.gmail.com>
Hello,
On Mon 06-02-12 00:14:58, Michel Lespinasse wrote:
> I would like to attend the LSF/MM summit in April this year. I do not
> have any formal topic proposals at this point; however there are
> several MM areas I am interested in:
>
> - mmap_sem locking: I have done some work in the past to reduce
> mmap_sem hold times when page faults wait for transfering file pages
> from disk, as well as during large mlock operations. However mmap_sem
> can still be held for long times today when write page faults trigger
> dirty write throttling, or when the system is under memory pressure
> and page allocations within the page fault handler hit the ttfp path
> (I have some pending work in these areas that I'd like to submit
> shortly). This is an area that hasn't been much invested in, probably
> because the fact that most users only need a read lock suffices to
> mask the issues in many cases. However I expect it to become more
> important as we keep improving performance isolation between
> processes. One way we frequently hit mmap_sem related issues at Google
> is when building monitoring mechanisms that are expected to stay
> responsive when the monitored systems get into bad memory pressure
> situations.
I'd be interested in this. Holding mmap_sem during write page faults
(->page_mkwrite) is causing problems with lock ordering when handling
filesystem freezing. I hope I can solve the problems by dropping mmap_sem
when we see filesystem is frozen, wait for it to thaw, retake mmap_sem and
return VM_FAULT_RETRY but I'd be happy for a less hacky solution...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-02-06 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 8:14 [ATTEND] LSF/MM conference Michel Lespinasse
2012-02-06 10:30 ` Jan Kara [this message]
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=20120206103024.GA6890@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=walken@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 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).