public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: jeff shia <tshxiayu@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: userspace filesystem Vs kernelspace filesystem
Date: Tue, 17 Jan 2006 23:55:05 -0500	[thread overview]
Message-ID: <1137560106.3587.57.camel@mindpipe> (raw)
In-Reply-To: <7cd5d4b40601172045j531a21b3y41db1dfbf84b769f@mail.gmail.com>

On Wed, 2006-01-18 at 12:45 +0800, jeff shia wrote:
> Hello,everyone!
> 
> Linux kernel provides vfs for the various physical filesystems.The
> profit we get from the
> VFS is just the standard interface it provides such as read and write?
> 
> Can we implement a user space filesystem which is actually a library?I
> think it will be
> faster than kernel space filesystem through the vfs layer.
> 
> Any suggestions or commnets?

Search list archives for FUSE (Filesystem in USErspace).

Lee


      reply	other threads:[~2006-01-18  4:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18  4:45 userspace filesystem Vs kernelspace filesystem jeff shia
2006-01-18  4:55 ` Lee Revell [this message]

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=1137560106.3587.57.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tshxiayu@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox