All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Cooper <joe@swelltech.com>
To: Marc-Christian Petersen <m.c.p@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: CONFIG_REISERFS_RAW (http://www.namesys.com/config.html)
Date: Tue, 18 Feb 2003 12:17:39 -0600	[thread overview]
Message-ID: <3E5278C3.7030608@swelltech.com> (raw)
In-Reply-To: <200302161452.21451.m.c.p@gmx.net>

You don't want to use it...

But if you do:

http://swelltech.com/pengies/joe/squidng.html

This page has the last versions of both the Squid and ReiserFS that have 
this feature.  It hasn't been supported in over two years, and it wasn't 
a trivial set of patches even then...I doubt you'd have much hope of 
getting either working in recent versions of Squid or kernel without 
significant help from both projects (probably paid help--this is deep 
code, and a lot of work to integrate).  It was a pretty darned fast 
Squid, though.

Marc-Christian Petersen wrote:
> Hi all,
> 
> can anyone tell me where I can find this code:
> 
> 
> CONFIG_REISERFS_RAW
>     Setting this to yes will enable a set of ioctls that provide raw
>     interface to the ReiserFS tree, bypass the directories, and
>     automatically remove aged files. This is an experimental feature
>     designed for squid cache directories. See Documentation/filesystems/reiserfs_raw.txt
>     This was designed specifically to use ReiserFS as a back-end for
>     the Squid. The general idea is that it is possible to bypass all
>     filesystem overhead and to directly address the ReiserFS internal
>     tree. This is not in the stock kernels. 
> 
> ?
> 
> Thanks.
> 
> ciao, Marc


-- 
Joe Cooper <joe@swelltech.com>
Web caching appliances and support.
http://www.swelltech.com


  reply	other threads:[~2003-02-18 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16 13:52 CONFIG_REISERFS_RAW (http://www.namesys.com/config.html) Marc-Christian Petersen
2003-02-18 18:17 ` Joe Cooper [this message]
2003-02-18 18:20   ` Joe Cooper
2003-02-18 18:33   ` Hans Reiser

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=3E5278C3.7030608@swelltech.com \
    --to=joe@swelltech.com \
    --cc=m.c.p@gmx.net \
    --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.