Re: Is there a "make hole" (truncate in middle) syscall?

["Jörn Engel" <joern@wohnheim.fh-wedel.de>]

On Mon, 15 December 2003 23:43:10 -0600, Rob Landley wrote:
> On Monday 15 December 2003 06:47, Jörn Engel wrote:
> 
> > Anyway, what updatedb, userspace defragmenters etc. need is a
> > notification, what has changed.
> 
> Most of this infrastructure is there already.  Documentation/dnotify.txt.

Right, although that specific implementation only cares about things
like konqueror not constantly polling one specific directory.

> > - updatedb is even worse
> > because it doesn't even notice that *anything* has changed, much less
> > what change happened.
> 
> You don't WANT it to.  You want to batch up the work so that if a file changes
> every thirty seconds you're not constantly being woken up to deal with it 
> again!

Well, *I* sure want it to.  Batching things up is fine, just the
current implementation isn't.

Yeah, it is good enough most of the time, so noone cares enough.

> > For updatedb there is.
> 
> I'm not talking about updatedb.

Then talk about checking for zero runs.  Same thing.  Either you have
to read *everything* from disk, so you don't want to do this too
often, or you need a way to figure out, what has changes since the
last run.

Or talk about updates, same thing as well.

What we do right now is basically polling, a very expensive and
therefore infrequent polling.  Sure, it works, but it's far from
perfect.


Anyway, subject has drifted away allready and we sure won't reach
agreement.  Doesn't matter anyway as long as noone provides the
patches, so let's just drop the thread, ok?

Jörn

-- 
/* Keep these two variables together */
int bar;