From: Robert Love <rml@novell.com>
To: Steve French <smfrench@austin.rr.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: which ioctls matter across filesystems
Date: Fri, 29 Apr 2005 16:57:52 -0400 [thread overview]
Message-ID: <1114808272.6682.158.camel@betsy> (raw)
In-Reply-To: <42729F4F.2020209@austin.rr.com>
On Fri, 2005-04-29 at 15:55 -0500, Steve French wrote:
> I believe that the spotlight facility of MacOS, and the somewhat similar
> Longhorn feature (think Google desktop search/indexing on steroids)
> qualify as killer-apps. I am concerned about how to do better with our
> implementations across a distributed (NFS, CIFS etc.) network. And of
> course coalescing async notifications most efficiently is a fascinating
> and difficult area to do right - for servers at least.
If we had some way to efficiently coalesce events, even non-remote stuff
would drool. Beagle (our Spotlight killer) would love it.
First thing is, the events cannot be stored in a linked list. ;-)
Robert Love
next prev parent reply other threads:[~2005-04-29 20:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 19:22 which ioctls matter across filesystems Steve French
2005-04-29 19:53 ` Trond Myklebust
2005-04-29 20:03 ` Robert Love
2005-04-29 20:42 ` Trond Myklebust
2005-04-29 20:47 ` Robert Love
2005-04-29 21:13 ` Trond Myklebust
2005-04-29 21:22 ` Steve French
2005-04-29 21:38 ` Trond Myklebust
2005-04-29 20:55 ` Steve French
2005-04-29 20:57 ` Robert Love [this message]
2005-04-29 21:05 ` Steve French
2005-04-29 20:47 ` Steve French
2005-04-29 20:50 ` Robert Love
2005-04-29 21:00 ` Steve French
2005-04-29 20:32 ` Steve French
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=1114808272.6682.158.camel@betsy \
--to=rml@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@austin.rr.com \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.