From owner-freebsd-hackers Mon Apr 8 11:50:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA16154 for hackers-outgoing; Mon, 8 Apr 1996 11:50:23 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA16147 for ; Mon, 8 Apr 1996 11:50:18 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.6.12/8.6.12) with ESMTP id LAA02562; Mon, 8 Apr 1996 11:48:28 -0700 Message-Id: <199604081848.LAA02562@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: Thomas Roell cc: Terry Lambert , msmith@atrad.adelaide.edu.au, hackers@FreeBSD.org, jkh@time.cdrom.com, roell@xinside.com Subject: Re: The F_SETOWN problem.. In-reply-to: Your message of "Mon, 08 Apr 1996 12:03:13 +0200." <199604081003.MAA00330@blah.a.isar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Apr 1996 11:48:27 -0700 From: "Amancio Hasty Jr." Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk If you have a good idea and you encounter a lot of resistance from this group it means that the group wants you to implement it 8) Cheers, Amancio >>> Thomas Roell said: > In your message of 7 April 1996 you write: > > > You can do the same thing without needing another process if you popen > > a fipe and write events to yourself that can then be selected upon. > > > > THis might very well fix your buffering id 1K vs. 6k (5k pipe + 1k kernel) > > is enough to fix the problem for you. > > I think you don't get it. The problem is no matter what I do, select() > will be only called rarely, which means that a pipe would not help at > all. Increasing the buffer size by any means just moves the problem to > a different threshold, rather than solving it. > > Just another example. We are (aehm from the sales prespective will be) > supporting HW-MPEG playback. The MPEG chip is fed with data > asynchronously via periodical SIGALARM calls. It is easily possible > that depending upon your bitstream, that for a while the X-Server will > not get back to the select() at all. > > > > Right. This is what SVR4 (except Solaris), SCO and AIX are doing. > > > > Well. It seems that you really want a fix in another area of BSD, > > and that this fix is just a software fix to the fact that the other > > area is broken. 8-). > > What I want is being able to open multple /dev/ttyd* devices and get a > SIGIO if there is new input available. > > - Thomas > -- > Denver Office THOMAS ROELL /\ Das Reh springt hoc h, > +1(303)298-7478 X INSIDE INC / \/\ das Reh springt wei t, > 1801 Broadway, Suite 1710 / \ \/\ was soll es tu n, > Denver, CO 80202 roell@xinside.com / Oelch! \ \ es hat ja Zei t. >