All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grzegorz Jaśkiewicz" <gryzman@gmail.com>
To: Faraz S <farazs@calsoftinc.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Comments about indexing and query solving in user land
Date: Mon, 6 Sep 2004 14:51:59 +0200	[thread overview]
Message-ID: <2f4958ff040906055172c36214@mail.gmail.com> (raw)
In-Reply-To: <-3757055227027460326@unknownmsgid>

On Mon, 06 Sep 2004 14:32:34 +0530, Faraz S <farazs@calsoftinc.com> wrote:
>         In our project http://sourceforge.net/projects/linuxsfs-tm/ we did the
> attribute indexing and query parsing in the user-space and we had hooks
> in the VFS which communicated with the user-space deamons. As far as
> directory listing is concerned we had a in kernel-recordset cache
> (hashed on the query). The listing were pretty efficient.
> 
>         But the real problem occured when a large number of files were copied
> in the onto our file system. All the files now need to be indexed in the
> user space , leading to mode switch. That was pathetically slooow. The
> entire 2.4 sources were copied in 5-6 hours. I think this problem could
> be solved by batching requests the user space deamon.  Then u have all
> the problems on missing out on indexing on a large set of files.
I think that should give you pretty much explanation why whole VFS
layer and filesystems are in kernel not in user space. That's where
such sort of thing belongs to. I have no doubts.
  


-- 
GJ

       reply	other threads:[~2004-09-06 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <-3757055227027460326@unknownmsgid>
2004-09-06 12:51 ` Grzegorz Jaśkiewicz [this message]
2004-09-07 20:09   ` Comments about indexing and query solving in user land daniel.poelzleithner
2004-09-06  9:02 Faraz S

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=2f4958ff040906055172c36214@mail.gmail.com \
    --to=gryzman@gmail.com \
    --cc=farazs@calsoftinc.com \
    --cc=reiserfs-list@namesys.com \
    /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.