From: Minchan Kim <minchan@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, John Stultz <john.stultz@linaro.org>
Subject: [LSF/MM TOPIC] volatile range: part 2
Date: Thu, 23 Jan 2014 15:21:28 +0900 [thread overview]
Message-ID: <20140123062128.GB14369@bbox> (raw)
Last year, there was discussion about volatile range but it seems
there wasn't no progress because John and I were stucked other
urgent works.
Recently, we modified many part of volatile range and submit
test code for volatile range anonymous part.
http://lwn.net/Articles/578761/
But still we didn't get indepth code review and many feedback.
It makes very hard to proceed that work.
I believe it's really nice concept and other OSes already similar
system call so lack of interesting from other MM guys is totally
my fault.
In this summit, I will summarize current status and known problems
I'm thinking so I hope lots of feedback and you guys will give a
time slot to review.
Thanks.
--
Kind regards,
Minchan Kim
--
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:[~2014-01-23 6:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140123062128.GB14369@bbox \
--to=minchan@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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.