Re: An FS question perhaps... non blocking I/O.

1999-09-17 Thread John-Mark Gurney
John Polstra scribbled this message on Sep 12: > In article <[EMAIL PROTECTED]>, > Garrett Wollman <[EMAIL PROTECTED]> wrote: > > [POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE] > > > It is probably undocumented. I was a bit reluctant to document it > > since I know that the interface is not co

Re: An FS question perhaps... non blocking I/O.

1999-09-17 Thread John W. DeBoskey
> In message <[EMAIL PROTECTED]>, John Polstra writes: > > >> ugh, why aren't you extending poll to work on files and directories to > >> get this info?? it would make MUCH more sense to extend poll to do this.. > >> > >> any specific reason why it wasn't done this way? > > > >Yes. Last time I

Re: An FS question perhaps... non blocking I/O.

1999-09-17 Thread Warner Losh
In message <[EMAIL PROTECTED]> John Polstra writes: : There are now 63000 files and directories in the repository. : That's 2**3 * 3**2 * 5**3 * 7. If we concatenate the exponents, : we get 3231, which is 3**2 * 359. Repeating, we get 21, which : is 3 * 7. One more repetition an

Re: An FS question perhaps... non blocking I/O.

1999-09-17 Thread John Polstra
Poul-Henning Kamp wrote: >>Somehow the thought of a 63,000-element pollfd array leaves me cold. > > Sounds like something Bruce would do :-) It could be worse. Satoshi, for example, would say something like: There are now 63000 files and directories in the repository. That's 2**3 * 3**

Re: An FS question perhaps... non blocking I/O.

1999-09-17 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, John Polstra writes: >> ugh, why aren't you extending poll to work on files and directories to >> get this info?? it would make MUCH more sense to extend poll to do this.. >> >> any specific reason why it wasn't done this way? > >Yes. Last time I checked, our CV

Re: An FS question perhaps... non blocking I/O.

1999-09-17 Thread John Polstra
John-Mark Gurney wrote: > John Polstra scribbled this message on Sep 12: >> >> Just to avoid duplicated effort: I currently have work in progress >> on a "fslog" pseudo-device. It enables you to monitor a filesystem >> and receive notifications for all interesting changes to files and >> direct

Re: An FS question perhaps... non blocking I/O.

1999-09-13 Thread John Polstra
In article <[EMAIL PROTECTED]>, Tony Finch <[EMAIL PROTECTED]> wrote: > > Are there any standard APIs for doing file meta-operations > asynchronously? (open, close, creat, link, unlink, etc.) I only know of one way to do that. Hand the operation off to a separate process, using the FD-passing

Re: An FS question perhaps... non blocking I/O.

1999-09-13 Thread Warner Losh
In message <[EMAIL PROTECTED]> John Polstra writes: : My personal interest is to allow a CVSup master server to avoid : doing a tree walk whenever a client connects. I want to provide the : functionality of the old "supscan" utility, but in real time. Also useful for tasty /dev/ persistance in a

Re: An FS question perhaps... non blocking I/O.

1999-09-13 Thread Dominic Mitchell
On Sun, Sep 12, 1999 at 10:56:42AM -0700, John Polstra wrote: > Just to avoid duplicated effort: I currently have work in progress > on a "fslog" pseudo-device. It enables you to monitor a filesystem > and receive notifications for all interesting changes to files and > directories. This includ

Re: An FS question perhaps... non blocking I/O.

1999-09-12 Thread John Polstra
Garrett Wollman wrote: > < said: > >> Just to avoid duplicated effort: I currently have work in progress >> on a "fslog" pseudo-device. It enables you to monitor a filesystem >> and receive notifications for all interesting changes to files and >> directories. > > However, this is not necessar

Re: An FS question perhaps... non blocking I/O.

1999-09-12 Thread Garrett Wollman
< said: > Just to avoid duplicated effort: I currently have work in progress > on a "fslog" pseudo-device. It enables you to monitor a filesystem > and receive notifications for all interesting changes to files and > directories. However, this is not necessarily duplicative of making polling o

Re: An FS question perhaps... non blocking I/O.

1999-09-12 Thread John Polstra
Rodney W. Grimes wrote: > > COOL!! And these mods could make a really nice addition to system > auditing tools required by high security systems. Do you pass anytype > of ``who done it'' via fslog? As of now, no. But it would be easy to add, and I think it's a great idea. Thanks! John To

Re: An FS question perhaps... non blocking I/O.

1999-09-12 Thread Tony Finch
Julian Elischer <[EMAIL PROTECTED]> wrote: > >The Posix AIO calls that john implememted are the best way of doing this. Are there any standard APIs for doing file meta-operations asynchronously? (open, close, creat, link, unlink, etc.) Tony. -- f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECT

Re: An FS question perhaps... non blocking I/O.

1999-09-12 Thread Rodney W. Grimes
> In article <[EMAIL PROTECTED]>, > Garrett Wollman <[EMAIL PROTECTED]> wrote: > > [POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE] > > > It is probably undocumented. I was a bit reluctant to document it > > since I know that the interface is not correct. One of these days, > > I (or more likel

Re: An FS question perhaps... non blocking I/O.

1999-09-12 Thread John Polstra
In article <[EMAIL PROTECTED]>, Garrett Wollman <[EMAIL PROTECTED]> wrote: [POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE] > It is probably undocumented. I was a bit reluctant to document it > since I know that the interface is not correct. One of these days, > I (or more likely some enterpris

Re: An FS question perhaps... non blocking I/O.

1999-09-09 Thread Ville-Pertti Keinonen
Luigi Rizzo <[EMAIL PROTECTED]> writes: > Is there any way to guarantee (more or less strictly, see below) > that when i issue a read() on a file (a real file coming from a > UFS i mean) such read will not block because data from the disk is > not in memory yet, yet avoid that i end up in a busy

RE: An FS question perhaps... non blocking I/O.

1999-09-09 Thread Garrett Wollman
< said: > I just checked, the poll(2) listed at > http://www.freebsd.org/cgi/man.cgi?query=poll&apropos=0&sektion=0&manpath=Fr > eeBSD+4.0-current&format=html as being from 4.0-current is dated Sept 7, > 1996; either the man page search on the web is out of date or this is an > undocumented bit

RE: An FS question perhaps... non blocking I/O.

1999-09-09 Thread Kelly Yancey
eebsd/Team-FreeBSD/ "The ultimate result of shielding men from the effects of folly is to fill the world with fools." - Herbert Spencer > -Original Message- > From: Juha Nurmela [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 09, 1999 3:26 PM > To: Kelly Yan

Re: An FS question perhaps... non blocking I/O.

1999-09-09 Thread Kelly Yancey
> Date: Thu, 9 Sep 1999 16:18:57 +0200 (MET DST) > From: Luigi Rizzo <[EMAIL PROTECTED]> > Subject: An FS question perhaps... non blocking I/O. > [ ... snip ... ] > > The app i have in mind is squid-like, which, if i understand > well, is a > single process loo

Re: An FS question perhaps... non blocking I/O.

1999-09-09 Thread Julian Elischer
The Posix AIO calls that john implememted are the best way of doing this. On Thu, 9 Sep 1999, Luigi Rizzo wrote: > Hi, > > please redirect to the appropriate forum if appropriate. > > There is one thing i don't completely understand with non-blocking > FS operation. > > Is there any way to g

An FS question perhaps... non blocking I/O.

1999-09-09 Thread Luigi Rizzo
Hi, please redirect to the appropriate forum if appropriate. There is one thing i don't completely understand with non-blocking FS operation. Is there any way to guarantee (more or less strictly, see below) that when i issue a read() on a file (a real file coming from a UFS i mean) such read wi