netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mingo@elte.hu, linux-mm@kvack.org,
	hpa@zytor.com, aarcange@redhat.com
Subject: Re: [PATCHv2 1/2] mm: export use_mm/unuse_mm to modules
Date: Wed, 16 Sep 2009 22:43:45 -0700	[thread overview]
Message-ID: <20090916224345.3b5212b4.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090917053817.GB6770@redhat.com>

On Thu, 17 Sep 2009 08:38:18 +0300 "Michael S. Tsirkin" <mst@redhat.com> wrote:

> Hi Andrew,
> On Tue, Aug 11, 2009 at 03:10:10PM -0700, Andrew Morton wrote:
> > On Wed, 12 Aug 2009 00:27:52 +0300
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > 
> > > vhost net module wants to do copy to/from user from a kernel thread,
> > > which needs use_mm (like what fs/aio has).  Move that into mm/ and
> > > export to modules.
> > 
> > OK by me.  Please include this change in the virtio patchset.  Which I
> > shall cheerfully not be looking at :)
> 
> The virtio patches are somewhat delayed as we are ironing out the
> kernel/user interface with Rusty. Can the patch moving use_mm to mm/ be
> applied without exporting to modules for now? This will make it easier
> for virtio which will only have to patch in the EXPORT line.

That was 10,000 patches ago.

> I also have a small patch optimizing atomic usage in use_mm (which I did for
> virtio) and it's easier to apply it if the code is in the new place.
> 
> If ok, pls let me know and I'll post the patch without the EXPORT line.

Please just send them all out.

--
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:[~2009-09-17  5:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1249992497.git.mst@redhat.com>
2009-08-11 21:27 ` [PATCHv2 1/2] mm: export use_mm/unuse_mm to modules Michael S. Tsirkin
2009-08-11 22:10   ` Andrew Morton
2009-09-17  5:38     ` Michael S. Tsirkin
2009-09-17  5:43       ` Andrew Morton [this message]
2009-08-11 21:28 ` [PATCHv2 2/2] vhost_net: a kernel-level virtio server Michael S. Tsirkin
2009-08-12  0:06   ` Gregory Haskins
2009-08-12  9:02     ` Michael S. Tsirkin
2009-08-12 13:01       ` Gregory Haskins
2009-08-12 13:25         ` Michael S. Tsirkin
2009-08-12 13:41           ` Gregory Haskins
2009-08-12 13:47             ` Michael S. Tsirkin
2009-08-12 14:11           ` Paul E. McKenney
2009-08-12 14:15             ` Michael S. Tsirkin
2009-08-12 15:26               ` Paul E. McKenney
2009-08-12 15:51                 ` Michael S. Tsirkin
2009-08-12 16:06                   ` Paul E. McKenney
2009-08-12 10:52     ` Michael S. Tsirkin

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=20090916224345.3b5212b4.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@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 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).