Re: different FD_SETSIZE on a remote than a local disk?
Re: different FD_SETSIZE on a remote than a local disk?
- Subject: Re: different FD_SETSIZE on a remote than a local disk?
- From: "Jordan K. Hubbard" <email@hidden>
- Date: Sun, 12 Mar 2006 13:43:45 -0800
However, i'm running into a problem -- the C++ server can create the test files (i've successfully tested up to 10000 of them on my 1.5ghz 12" PowerBook, and it can go much higher than that I think) fine on the local disk, but when trying to do so on a remote disk (my dual 2ghz G5, across AE), it can't make any more than 1248. This is with the filedescriptor limit set to 10000 (via /bin/csh limit), so it appears that the filedescriptor limit that csh sets isn't honored on a remote disk.
What's the point of registering kqueue() notifications against files on a remote disk? If you modify them on the system doing the monitoring then fine, it will catch them, but if any other client of that remote filesystem (or the server machine itself) modifies them, you won't.
It's also not very performant to monitor 1000's of files like this. You can do it this way, but the overheads are non-trivial.
- Jordan
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden