Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262082AbVDRONW (ORCPT ); Mon, 18 Apr 2005 10:13:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262086AbVDROM6 (ORCPT ); Mon, 18 Apr 2005 10:12:58 -0400 Received: from stat16.steeleye.com ([209.192.50.48]:29159 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id S262082AbVDROMw (ORCPT ); Mon, 18 Apr 2005 10:12:52 -0400 Subject: Re: increasing scsi_max_sg / max_segments for scsi writes/reads From: James Bottomley To: sai narasimhamurthy Cc: "Randy.Dunlap" , SCSI Mailing List , Linux Kernel In-Reply-To: <20050418061723.49716.qmail@web54105.mail.yahoo.com> References: <20050418061723.49716.qmail@web54105.mail.yahoo.com> Content-Type: text/plain Date: Mon, 18 Apr 2005 09:12:41 -0500 Message-Id: <1113833561.4998.10.camel@mulgrave> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 25 On Sun, 2005-04-17 at 23:17 -0700, sai narasimhamurthy wrote: > I tried working on scsi_malloc to increase burst size > , but to no avail ..all I got was hanged system every > time I started data transfers! > Has anyone worked on scsi_malloc , I am still trying > to figure out what changes were made in 2.6 to > overcome this problem of limited bursts. The change in 2.6 was to dump scsi_malloc and use mempools instead for the sg list. > Any pointers are very greatly welcome...I have never > worked on this part of the code before . Upgrade to 2.6 ... seriously ... what you're trying to do is what 2.6 was designed for. James - 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/