From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH] virtio_blk: don't bounce highmem requests
Date: Tue, 23 Jun 2009 16:42:52 +0930
Message-ID: <200906231642.52848.rusty@rustcorp.com.au>
References: <20090619182022.GA10999@lst.de> <20090620183215.GA24936@lst.de>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
To: Christoph Hellwig <hch@lst.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from ozlabs.org ([203.10.76.45]:59874 "EHLO ozlabs.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752907AbZFWHMw (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 23 Jun 2009 03:12:52 -0400
In-Reply-To: <20090620183215.GA24936@lst.de>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Sun, 21 Jun 2009 04:02:15 am Christoph Hellwig wrote:
> Looks like I sent a patch that doesn't actually compile because qui
> decided to apply those fixes to a different one.  Here's the correc
> one:
>
> --
>
> Subject: virtio_blk: don't bounce highmem requests
> From: Christoph Hellwig <hch@lst.de>
>
> By default a block driver bounces highmem requests, but virtio-blk is
> perfectly fine with any request that fit into it's 64 bit addressing
> scheme, mapped in the kernel virtual space or not.

Thanks, applied.

I had no idea we had to set a bounce limit; wonder what else the driver 
doesn't do?

Thanks,
Rusty.