Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261426AbUK1K2f (ORCPT ); Sun, 28 Nov 2004 05:28:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261427AbUK1K2f (ORCPT ); Sun, 28 Nov 2004 05:28:35 -0500 Received: from quechua.inka.de ([193.197.184.2]:60363 "EHLO mail.inka.de") by vger.kernel.org with ESMTP id S261426AbUK1K2d (ORCPT ); Sun, 28 Nov 2004 05:28:33 -0500 From: Bernd Eckenfels To: linux-kernel@vger.kernel.org Subject: Re: Problem with ioctl command TCGETS Organization: Deban GNU/Linux Homesite In-Reply-To: X-Newsgroups: ka.lists.linux.kernel User-Agent: tin/1.7.6-20040906 ("Baleshare") (UNIX) (Linux/2.6.8.1 (i686)) Message-Id: Date: Sun, 28 Nov 2004 11:28:29 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1070 Lines: 26 In article you wrote: > * @fd file descriptor > * @param name of the parameter to get/set > * @dir direction flag indicating either get, set, or set-get > * @value value to set parameter to (set) or store current value into (get) > * @size size of value > */ > int fparam(int fd, const char *param, int dir, void *value, size_t size); > > I know it's been talked about in the past. Is anyone interested? 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. The syscall should also allow cunking in response, unless we remove all high-volumne answers from it. Gruss Bernd - 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/