fam
[Top] [All Lists]

Re: [fam] dnotify

To: aghaffar@xxxxxxxxxxxx
Subject: Re: [fam] dnotify
From: "Rusty Ballinger" <rusty@xxxxxxxxxxxxxxxxxx>
Date: Tue, 13 Mar 2001 18:27:42 -0800
Cc: fam@xxxxxxxxxxx
In-reply-to: Atif Ghaffar <aghaffar@xxxxxxxxxxxx> "Re: [fam] dnotify" (Mar 12, 1:29pm)
References: <3AABB6FB.6FC57101@xxxxxxxxxxxx> <10103120243.ZM21359@xxxxxxxxxxxxxxxxxx> <3AACC13F.26B44561@xxxxxxxxxxxx>
Reply-to: rusty@xxxxxxx
Sender: owner-fam@xxxxxxxxxxx
> > - One potential problem is that with dnotify, you need one open fd per
> >   monitored directory.  (Of course, for applications which only monitor
> >   one directory anyway, this isn't a problem.)
>
> Isnt there a similar problem with imon kernel-patch.

No, a FAMConnection has one file descriptor which can be used for all
requests.  You don't have to keep one open file descriptor per monitored
file or directory.

> I tried to use imon+fam for a file mirroring system for webservers but
> failed cause I had probs with some kmallocs etc.
> I have reported this to the list before.

Yeah, that's definitely a bug, but I haven't looked into it yet.  (Did you
try Johan's change, replacing kmalloc/kfree with vmalloc/vfree in imon's
hash table code?  I think he said it fixed the kmalloc failure but didn't
fix the problem, as his stuff was still croaking on the 926th directory.
Does that happen on your system too?)

--Rusty

--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>