From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 22 20:37:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3B4716A577 for ; Wed, 22 Nov 2006 20:37:17 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE85243DF2 for ; Wed, 22 Nov 2006 20:35:21 +0000 (GMT) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Gmyok-0004NF-Kw for freebsd-hackers@freebsd.org; Wed, 22 Nov 2006 21:35:39 +0100 Received: from 89-172-62-47.adsl.net.t-com.hr ([89.172.62.47]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Nov 2006 21:35:38 +0100 Received: from ivoras by 89-172-62-47.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Nov 2006 21:35:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Wed, 22 Nov 2006 21:35:20 +0100 Lines: 13 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-62-47.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) Sender: news Subject: Kqueue write event position? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2006 20:37:17 -0000 >From the kqueue(2) manual: """ EVFILT_VNODE Takes a file descriptor as the identifier and the events to watch for in fflags, and returns when one or more of the requested events occurs on the descriptor. The events to monitor are:... """ I'm interested in NOTE_WRITE, but is there a way to find out where has the write been performed (position and length)? If not, how difficult would it be to expand the API so this information is included?