Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 19 Apr 2002 05:27:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 19 Apr 2002 05:27:29 -0400 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:1549 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Fri, 19 Apr 2002 05:27:29 -0400 Subject: Re: Bio pool & scsi scatter gather pool usage To: lord@sgi.com (Stephen Lord) Date: Fri, 19 Apr 2002 09:58:36 +0100 (BST) Cc: akpm@zip.com.au (Andrew Morton), alan@lxorguk.ukuu.org.uk (Alan Cox), peloquin@us.ibm.com (Mark Peloquin), linux-kernel@vger.kernel.org In-Reply-To: <3CBFC755.50106@sgi.com> from "Stephen Lord" at Apr 19, 2002 02:29:25 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > But this gets you lowest common denominator sizes for the whole > volume, which is basically the buffer head approach, chop all I/O up > into a chunk size we know will always work. Any sort of nasty boundary > condition at one spot in a volume means the whole thing is crippled > down to that level. It then becomes a black magic art to configure a > volume which is not restricted to a small request size. Its still cheaper to merge bio chains than split them. The VM issues with splitting them are not nice at all since you may need to split a bio to write out a page and it may be the last page - 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/