All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Robin Holt <holt@sgi.com>
Cc: Cliff Wickman <cpw@sgi.com>,
	linux-mm@kvack.org, aarcange@redhat.com, mgorman@suse.de
Subject: Re: [PATCH] mm: export mmu notifier invalidates
Date: Wed, 13 Feb 2013 12:11:49 -0800	[thread overview]
Message-ID: <20130213121149.25a0e3bd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20130213150340.GJ3460@sgi.com>

On Wed, 13 Feb 2013 09:03:40 -0600
Robin Holt <holt@sgi.com> wrote:

> > But in a better world, the core kernel would support your machines
> > adequately and you wouldn't need to maintain that out-of-tree MM code. 
> > What are the prospects of this?
> 
> We can put it on our todo list.  Getting a user of this infrastructure
> will require changes by Dimitri for the GRU driver (drivers/misc/sgi-gru).
> He is currently focused on getting the design of some upcoming hardware
> finalized and design changes tested in our simulation environment so he
> will be consumed for the next several months.
> 
> If you would like, I can clean up the driver in my spare time and submit
> it for review.  Would you consider allowing its inclusion without the
> GRU driver as a user?

>From Cliff's description it sounded like that driver is
duplicating/augmenting core MM functions.  I was more wondering
whether core MM could be enhanced so that driver becomes obsolete?

> In the transition period, could we allow this change in and then remove
> the exports as part of that driver being accepted?  That would help us
> with an upcoming distro release.

I'm OK with this patch for 3.9-rc1.

--
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:[~2013-02-13 20:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 21:35 [PATCH] mm: export mmu notifier invalidates Cliff Wickman
2013-02-12 21:57 ` Andrew Morton
2013-02-13 15:03   ` Robin Holt
2013-02-13 20:11     ` Andrew Morton [this message]
2013-02-13 21:03       ` Robin Holt
2013-02-14 21:08         ` Andrew Morton
2013-02-14 21:35           ` Robin Holt
2013-02-14 21:52             ` Andrew Morton
2013-02-14 22:25               ` Robin Holt
  -- strict thread matches above, loose matches on Subject: below --
2013-01-04 15:41 Cliff Wickman
2013-01-04 21:35 ` Christoph Hellwig
2013-01-04 22:09   ` Cliff Wickman
2013-01-07 14:14 ` Mel Gorman
2013-01-07 15:35   ` Andrea Arcangeli

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=20130213121149.25a0e3bd.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --cc=cpw@sgi.com \
    --cc=holt@sgi.com \
    --cc=linux-mm@kvack.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 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.