Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754452AbZKDNUW (ORCPT ); Wed, 4 Nov 2009 08:20:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752374AbZKDNUW (ORCPT ); Wed, 4 Nov 2009 08:20:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:4703 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752276AbZKDNUV (ORCPT ); Wed, 4 Nov 2009 08:20:21 -0500 Date: Wed, 4 Nov 2009 15:17:36 +0200 From: "Michael S. Tsirkin" To: Andi Kleen 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, akpm@linux-foundation.org Subject: Re: [PATCHv7 3/3] vhost_net: a kernel-level virtio server Message-ID: <20091104131735.GD8920@redhat.com> References: <20091103172422.GD5591@redhat.com> <878wema6o0.fsf@basil.nowhere.org> <20091104121009.GF8398@redhat.com> <20091104125957.GL31511@one.firstfloor.org> <20091104130828.GC8920@redhat.com> <20091104131533.GM31511@one.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091104131533.GM31511@one.firstfloor.org> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1666 Lines: 46 On Wed, Nov 04, 2009 at 02:15:33PM +0100, Andi Kleen wrote: > On Wed, Nov 04, 2009 at 03:08:28PM +0200, Michael S. Tsirkin wrote: > > On Wed, Nov 04, 2009 at 01:59:57PM +0100, Andi Kleen wrote: > > > > Fine? > > > > > > I cannot say -- are there paths that could drop the device beforehand? > > > > Do you mean drop the mm reference? > > No the reference to the device, which owns the mm for you. The device is created when file is open and destroyed when file is closed. So I think the fs code handles the reference counting for me: it won't call file cleanup callback while some userspace process has the file open. Right? > > > > > (as in do you hold a reference to it?) > > > > By design I think I always have a reference to mm before I use it. > > > > This works like this: > > ioctl SET_OWNER - calls get_task_mm, I think this gets a reference to mm > > ioctl SET_BACKEND - checks that SET_OWNER was run, starts virtqueue > > ioctl RESET_OWNER - stops virtqueues, drops the reference to mm > > file close - stops virtqueues, if we still have it then drops mm > > > > This is why I think I can call use_mm/unuse_mm while virtqueue is running, > > safely. > > Makes sense? > > Do you protect against another thread doing RESET_OWNER in parallel while > RESET_OWNER runs? Yes, I have a mutex in the device for that. Same with SET_BACKEND. > -Andi > > -- > ak@linux.intel.com -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/