From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261446AbUK1MSE (ORCPT ); Sun, 28 Nov 2004 07:18:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261448AbUK1MSE (ORCPT ); Sun, 28 Nov 2004 07:18:04 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:25990 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S261446AbUK1MSC (ORCPT ); Sun, 28 Nov 2004 07:18:02 -0500 Date: Sun, 28 Nov 2004 12:18:00 +0000 From: Al Viro To: Miklos Szeredi Cc: ecki-news2004-05@lina.inka.de, linux-kernel@vger.kernel.org Subject: Re: Problem with ioctl command TCGETS Message-ID: <20041128121800.GZ26051@parcelfarce.linux.theplanet.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 28, 2004 at 12:22:03PM +0100, Miklos Szeredi wrote: > > The set-get is supposed to be used for queries, too? The size of value is > > only used for the get case to describe the buffer length in that case? > > because otherwise the set-get case may require a short value in and a large > > answer structure out. > > You misunderstand the motivation. This is to get/set small compact > parameters, not huge structures or big data. Think get/setsockopt(). Think read(2)/write(2). We already have several barfbags too many, and that includes both ioctl() and setsockopt(). We are stuck with them for compatibility reasons, but why the hell would we need yet another one?