Date: Thu, 23 Nov 2006 12:54:24 +0200 From: "Vlad Galu" <dudu@dudu.ro> To: freebsd-hackers@freebsd.org Subject: Re: Kqueue write event position? Message-ID: <ad79ad6b0611230254k273bed6bh4543d42c311281ed@mail.gmail.com> In-Reply-To: <ek3u1h$5ai$1@sea.gmane.org> References: <ek2ca4$sft$1@sea.gmane.org> <ad79ad6b0611221309q85e37e5p224ba93d0b9c9b5@mail.gmail.com> <ek3p31$i69$1@sea.gmane.org> <ad79ad6b0611230222x21e68c8bxe86da349ffd7f7ec@mail.gmail.com> <ek3u1h$5ai$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/23/06, Ivan Voras <ivoras@fer.hr> wrote: > Vlad Galu wrote: > > > My guess is that it won't be remarcably high. However, you can > > create those files, add them to your notification list and randomly > > write bytes to them, to see how your system performs. One more > > suggestion, I think it would be better if, in case you extend the > > vnode API, you only send the size of the write in the data field of > > the kevent structure and you store the offset in your program and > > adding the size to it everytime an event occurs. > > The writes will not be sequential so I need both offset and length. > Eh I guess you can use udata for one of them, then. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ad79ad6b0611230254k273bed6bh4543d42c311281ed>