[haiku-development] Re: file modification watching

  • From: Clemens <clemens.zeidler@xxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 16 Aug 2011 10:25:35 +1200

On Fri, 12 Aug 2011 21:35:39 +1200, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:


ok, but in case of the index server this would be always the case because
the index server watches all nodes and requires the entry_ref for each
modified node...

Once the index server is included and active by default, we can still make
the addition of the extra fields unconditional or simplify the check by
maintaining per-volume counters for the listeners requiring those fields. At any rate the fact remains that, due the way the messaging works, sending two different messages is significantly more expensive than sending the larger message to all listeners. At least on the kernel side where it matters most,
since that's all done synchronously (i.e. slowing down the FS operation).


ok thanks,
another (IMHO a bit hacky) solution would be to add a userland listener for open and close. The index server then watch files that have been opened writeable and do the node-entry mapping by itself.

what do you think?

Regards,
        Clemens

Other related posts: