From: Theodore Ts'o <tytso@mit.edu>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] ZONE_DEVICE and Persistent Memory (was: Re: Draft agenda for the kernel summit)
Date: Mon, 19 Oct 2015 14:52:20 -0400 [thread overview]
Message-ID: <20151019185220.GA3068@thunk.org> (raw)
In-Reply-To: <20151019182923.GB5907@thunk.org>
On Mon, Oct 19, 2015 at 02:29:23PM -0400, Theodore Ts'o wrote:
> On Fri, Oct 16, 2015 at 05:08:21PM -0400, Jerome Glisse wrote:
> > On Thu, Oct 15, 2015 at 09:49:49AM -0700, Dave Hansen wrote:
> > > On 10/14/2015 05:17 PM, Dan Williams wrote:
> > > > I am wondering if it would be productive / good use of time to do a
> > > > direction check on the mm changes being done in support of large
> > > > persistent memory devices.
> > >
> > > I think there's probably an even wider discussion that we should have here.
> > >
> > > Beyond just ZONE_DEVICE, the sheer number of memory types is increasing
> > > fast, and our current solutions are, at best, inconsistent. We currently
> > > handle memory types as new zones, repurposed zones, pageblocks inside
> > > zones, or faux NUMA nodes.
> > >
> > > Are our current solutions too erratic?
> > > Do we need to solve these problems generally, or are we going to kill
> > > ourselves trying to make everyone happy?
> > > What types do we ignore today, but shouldn't?
> > > What types are coming down the pike?
> >
> > I think what i am working on (HMM and how to leverage GPU memory that is
> > not accessible by the CPU) apply here too. All features i am working on
> > imply that i have to dig through layers of code seeing if i can abuse an
> > existing mechanism to achieve something new.
> >
> > So i definitly think we should discuss where we are and where we want to
> > be.
>
> Dan, would you be willing to kick off the discussion?
Oops, sorry, it was pointed out to me that Dan isn't going to be at
the Kernel Summit. Jerome, would you be willing to kick off the
discussion and report back to Dan?
- Ted
next prev parent reply other threads:[~2015-10-19 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 0:17 Dan Williams
2015-10-15 16:49 ` Dave Hansen
2015-10-16 21:08 ` Jerome Glisse
2015-10-19 18:29 ` Theodore Ts'o
2015-10-19 18:52 ` Theodore Ts'o [this message]
2015-10-19 19:23 ` Dan Williams
2015-10-19 19:32 ` Jerome Glisse
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=20151019185220.GA3068@thunk.org \
--to=tytso@mit.edu \
--cc=j.glisse@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox