Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 16 Nov 2001 17:58:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 16 Nov 2001 17:58:19 -0500 Received: from postfix2-1.free.fr ([213.228.0.9]:4271 "HELO postfix2-1.free.fr") by vger.kernel.org with SMTP id convert rfc822-to-8bit; Fri, 16 Nov 2001 17:57:59 -0500 Date: Fri, 16 Nov 2001 21:12:33 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: "David S. Miller" Cc: , Subject: Re: [patch] block-highmem-all-18 In-Reply-To: <20011116.135409.118971851.davem@redhat.com> Message-ID: <20011116205140.J2032-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 16 Nov 2001, David S. Miller wrote: > From: G?rard Roudier > Date: Fri, 16 Nov 2001 19:59:02 +0100 (CET) > > On Fri, 16 Nov 2001, Jens Axboe wrote: > > > - Add sym2 can_dma_32 flag (me) > ^^^^^^^^^^ Pooaaahhh!:) What's this utter oddity ? > Only dma 32 ? :-) > > It is workaround for buggy drivers, when set it means that single SG > list entry request will be handled correctly. When clear it means > that single entry SG lists are to be avoided by the block layer. > > Many devices would explode when given single entry scatterlist. :( > > It's naming is questionable... that I agree with. The name should be > more suggestive to what it really means. For now, it humanly means that the device is able to dma decimal value 32 which does not look this great a feature, nor that serious a bug. :-) :o) Thanks, anyway, for the clarification. G?rard. - 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/