Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 17 Jul 2002 09:57:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 17 Jul 2002 09:57:33 -0400 Received: from leibniz.math.psu.edu ([146.186.130.2]:34231 "EHLO math.psu.edu") by vger.kernel.org with ESMTP id ; Wed, 17 Jul 2002 09:57:32 -0400 Date: Wed, 17 Jul 2002 10:00:24 -0400 (EDT) From: Alexander Viro To: Joerg Schilling cc: riel@conectiva.com.br, James.Bottomley@steeleye.com, linux-kernel@vger.kernel.org Subject: Re: IDE/ATAPI in 2.5 In-Reply-To: <200207171346.g6HDkb1l028358@burner.fokus.gmd.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1015 Lines: 24 On Wed, 17 Jul 2002, Joerg Schilling wrote: > Is there any problem with using a ioctl() from upper layer kernel to the low > level drivers (living under the SW raid) to reduce the number of retries to a > reasonable value in this case? > > The main design goal for UNIX as to keep it simple. There is no need for a > complex cross layer error control. ... and ioctl(2) is a gross violation of that design goal. Ask the authors of UNIX how they feel about that kludge, let alone propagation of said kludge beyond the TTY layer where it had originated (or about the entire v7 TTY layer, for that matter - v8 and later had thrown that crap away). If you care about design philosophy of UNIX - at the very least take a hard look at APIs you are using. Sheesh... - 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/