Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262466AbTIHOeA (ORCPT ); Mon, 8 Sep 2003 10:34:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262408AbTIHOeA (ORCPT ); Mon, 8 Sep 2003 10:34:00 -0400 Received: from ns.virtualhost.dk ([195.184.98.160]:64642 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S262466AbTIHOd5 (ORCPT ); Mon, 8 Sep 2003 10:33:57 -0400 Date: Mon, 8 Sep 2003 16:34:08 +0200 From: Jens Axboe To: Sven =?iso-8859-1?Q?K=F6hler?= Cc: linux-kernel@vger.kernel.org Subject: Re: [blockdevices/NBD] huge read/write-operations are splitted by the kernel Message-ID: <20030908143408.GT840@suse.de> References: <20030908085802.GH840@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 701 Lines: 21 On Mon, Sep 08 2003, Sven K?hler wrote: > >You'll probably find that if you bump the max_sectors count if your > >drive to 256 from 255 (that is the default if you haven't set it), then > >you'll see 128kb chunks all the time. > > > >See max_sectors[] array. > > To make it clear: > the kernel will never read or write more sectors at once than specified > in the max_sectors array (where every device has its own value), right? Correct -- Jens Axboe - 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/