Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 24 Oct 2002 07:39:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 24 Oct 2002 07:39:04 -0400 Received: from [195.20.32.236] ([195.20.32.236]:46785 "HELO euro.verza.com") by vger.kernel.org with SMTP id ; Thu, 24 Oct 2002 07:39:03 -0400 Date: Thu, 24 Oct 2002 13:45:04 +0200 From: Alexander Kellett To: Rik van Riel Cc: linux-kernel@vger.kernel.org Subject: Re: Linux v2.5.42 Message-ID: <20021024114504.GA18130@groucho.verza.com> Mail-Followup-To: Rik van Riel , linux-kernel@vger.kernel.org References:

Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Disclaimer: My opinions do not necessarily represent those of my employer Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 18 On Sun, Oct 13, 2002 at 05:57:06PM -0200, Rik van Riel wrote: > All you need is: > 1) a kernel level driver that can map devices, ie. a device mapper > 2) user space tools that can parse the volume metadata and tell the > kernel how to map each chunk at initialisation or mount time stupid user question here. does the dm stuff make vmware partition mounts easy without needing all the nbd overhead?, or would the mappings be so large that they negate the decrease in nbd overhead? Alex - 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/