public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sean R. Bright" <elixer@erols.com>
To: <linux-kernel@vger.kernel.org>
Subject: FS callback routines
Date: Mon, 8 Jan 2001 20:21:31 -0500	[thread overview]
Message-ID: <000c01c079db$78ab39e0$59aa0141@cc230545b> (raw)


	Ok, before I begin, don't shoot me down, but I had an idea for a kernel
modification and was wondering how feasible the group thought it was.

	I was writing a user space application to monitor a folder's contents.  The
folder itself contained 100 folders, and each of those contained 24 folders.
While writing the code to traverse the directory structure I realized that
instead of my software figuring out when things change, why not just have
the fs tell my application when something was updated.  For example, say we
had a function called watch_fs(), that took an inode reference and a
function pointer and maybe a bitmask of events to watch for.  When that
inode (or its children) were changed, why couldn't the fs code call the
callback function I specified?

	I have no idea how expensive this would be or if its even worth it at this
point.  It also wouldn't be portable at all considering that I know of no
other OS that does this (could be wrong).

	Like I said, I am not asking that this be (necessarily) implemented, I am
just curious as to what the percieved performance ramifications would be if
it were to implemented, say, by a virgin kernel developer ;)

	Thanks,
	Sean
	elixer@erols.com



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-09  1:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  1:21 Sean R. Bright [this message]
2001-01-09 11:22 ` FS callback routines Philipp Matthias Hahn
2001-01-09 11:34 ` Daniel Stodden
  -- strict thread matches above, loose matches on Subject: below --
2001-01-11 16:39 Jesse Pollard
2001-01-11 17:53 ` Daniel Phillips
2001-01-10 15:18 Jesse Pollard
2001-01-09 14:05 Jesse Pollard
2001-01-09 15:41 ` Daniel Phillips
2001-01-10 10:48   ` Jamie Lokier
2001-01-08 23:12 Michael D. Crawford
2001-01-09  2:37 ` Sean R. Bright
2001-01-09  3:48 ` David Weinehall
2001-01-09 13:07 ` Daniel Phillips
2001-01-10 10:56   ` Jamie Lokier
2001-01-10 18:25     ` Daniel Phillips
2001-01-11 14:30     ` Daniel Phillips
2001-01-11 15:37       ` Jamie Lokier
2001-01-11 16:11         ` Daniel Phillips

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000c01c079db$78ab39e0$59aa0141@cc230545b' \
    --to=elixer@erols.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox