From owner-freebsd-hackers Fri Dec 21 19:55:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cu518.adelaide.adsl.on.net (cu518.adelaide.adsl.on.net [150.101.236.10]) by hub.freebsd.org (Postfix) with ESMTP id 02FDE37B417; Fri, 21 Dec 2001 19:55:29 -0800 (PST) Received: from ns.aus.com (cu518.adsl.adelaide.on.net [127.0.0.1]) by cu518.adelaide.adsl.on.net (8.11.0/8.11.0) with ESMTP id fBM64U715680; Sat, 22 Dec 2001 16:34:31 +1030 Message-ID: <3C240E26.3070007@ns.aus.com> Date: Sat, 22 Dec 2001 15:07:58 +1030 From: Richard Sharpe Reply-To: rsharpe@ns.aus.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20010917 X-Accept-Language: en-us MIME-Version: 1.0 To: Mike Barcroft Cc: rsharpe@ns.aus.com, Alfred Perlstein , FreeBSD-hackers@FreeBSD.ORG Subject: Re: Adding si_fd to struct __siginfo ... References: <3C23AF6E.90202@ns.aus.com> <20011221164429.U48837@elvis.mu.org> <3C23C80B.6030509@ns.aus.com> <20011221223942.B59246@espresso.q9media.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Barcroft wrote: >Richard Sharpe writes: > >>>There was already a big mess of a discussion about how this would >>>be much better done via kqueue than with realtime signals. >>> >>>I guess if you can get a working implementation that is compatible >>>with the existing interfaces it would work, however it's a _much_ >>>better idea to use kqueue to deliver this sort of notification. >>> Well, it turns out that there are two problems with what I suggested: 1, signals are lossy, in that if multiple signals occur, only one might be delivered; and 2, there is no place to store any signal-related information in the kernel, in any case. So, it seems like kqueue is really the only game in town, but I will need an appropriate filter, and it would be nice if I could get some sort of async notification that there were events ready to be processed, as I really don't want to rewrite Samba completely, just to support kqueue ... Hmmm, perhaps the approach should be to signal that leases/oplocks have been broken, but provide the details via kqueue. >>> >>>And yes, it has been discussed in the lists already. >>> >>OK, I will go and look at the discussion ... >> > >Unfortunately this discussion mistakenly took place on a FreeBSD >mailing list intended for administrative-only issues, so it isn't >publicly available on our end. Luckily, a Samba mailing list was >on the CC line. You should be able to find it on the > archives circa September 2001. > >Best regards, >Mike Barcroft > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- Richard Sharpe, rsharpe@ns.aus.com, LPIC-1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message