Lines Matching refs:and

17    the file and thus, worse, pins the mount.  Dnotify is therefore infeasible
25    more fd's than are feasible to manage, and more fd's than are optimally
26    select()-able.  Yes, root can bump the per-process fd limit and yes, users
27    can use epoll, but requiring both is a silly and extraneous requirement.
30    want: Users initialize inotify, once, and add n watches, requiring but one
31    fd and no twiddling with fd limits.  Initializing an inotify instance two
33    cleanly--and we can, the idr layer makes stuff like this trivial--then we 
38    fd returns all watch events and also any potential out-of-band data.  If
41    - There would be no way to get event ordering.  Events on file foo and
47    - We'd have to maintain n fd's and n internal queues with state,
53      to manage and block on 1000 fd's via select?
63    Additionally, it _is_ possible to  more than one instance  and
64    juggle more than one queue and thus more than one associated fd.  There
65    need not be a one-fd-per-process mapping; it is one-fd-per-queue and a
73    file descriptor-based one that allows basic file I/O and poll/select.
74    Obtaining the fd and managing the watches could have been done either via a
78    and ioctl(2) or a couple of new system calls.  System calls beat ioctls.