All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Pritts <danno@internet2.edu>
To: Mike Fedyk <mfedyk@matchmail.com>, jds <jds@soltis.cc>,
	Ryan Underwood <nemesis-lists@icequake.net>,
	reiserfs-list@namesys.com, openafs-info@openafs.org
Subject: Re: [OpenAFS] Re: Problems with reiserfs when start OpenAFS 1.2.11-fc1 Segmentation fault with kernel 2.4.22-1.2174.nptl
Date: Thu, 4 Mar 2004 18:07:25 -0500	[thread overview]
Message-ID: <20040304230725.GA19887@internet2.edu> (raw)
In-Reply-To: <20040304071846.GB324@dbz.icequake.net>

On Thu, Mar 04, 2004 at 01:18:46AM -0600, Ryan Underwood wrote:
> > No, if you're going to be stacking filesystems, use ext2, not ext3.  You 
> > will get better performance, and there's no use in having two levels of 
> > journaling in this case.
> 
> You might also think about bigger than 100MB cache file.  A big cache
> helps out AFS client performance tremendously.  But definitely use ext2
> and not ext3 as others have said.

I realize it won't work out of the box, but has anyone given any
thought to putting the cache in tmpfs?

Seems like this might be the best of both worlds - when the system is low
on RAM it can use swap, but when you've got plenty of RAM you avoid the
overhead of writing the cache files to disk.

more flexible than memcache, faster than disk cache.  My understanding
(limited) of the tmpfs on linux suggests that it might be an easy change
to make in the code for someone who understood the data structions better
than i do ;)

mostly, just curious...can anyone say?

danno
--
dan pritts                                       danno@internet2.edu
systems administrator                            734/352-4953 office
internet2                                        734/834-7224 mobile

  reply	other threads:[~2004-03-04 23:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040304005117.M99283@soltis.cc>
2004-03-04  1:00 ` Problems with reiserfs when start OpenAFS 1.2.11-fc1 Segmentation fault with kernel 2.4.22-1.2174.nptl jds
2004-03-04  0:28   ` Ryan Underwood
2004-03-04  1:48     ` jds
2004-03-04  3:46       ` Mike Fedyk
2004-03-04  7:18         ` Ryan Underwood
2004-03-04 23:07           ` Dan Pritts [this message]
2004-03-05  1:40             ` [OpenAFS] " Ryan Underwood

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=20040304230725.GA19887@internet2.edu \
    --to=danno@internet2.edu \
    --cc=jds@soltis.cc \
    --cc=mfedyk@matchmail.com \
    --cc=nemesis-lists@icequake.net \
    --cc=openafs-info@openafs.org \
    --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.