xfs
[Top] [All Lists]

Re: [reiserfs-list] Re: benchmarks

To: Xuan Baldauf <xuan--reiserfs@xxxxxxxxxxx>
Subject: Re: [reiserfs-list] Re: benchmarks
From: Ragnar Kjørstad <reiserfs@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 16 Jul 2001 22:32:42 +0200
Cc: Nikita Danilov <NikitaDanilov@xxxxxxxxx>, Russell Coker <russell@xxxxxxxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, rsharpe@xxxxxxxxxx, Seth Mos <knuffie@xxxxxxxxx>, Federico Sevilla III <jijo@xxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, reiserfs-list@xxxxxxxxxxx
In-reply-to: <3B534B74.BDE19961@xxxxxxxxxxx>; from Xuan Baldauf on Mon, Jul 16, 2001 at 10:15:48PM +0200
References: <Pine.BSI.4.10.10107141752080.18419-100000@xxxxxxxxxxxxx> <3B5169E5.827BFED@xxxxxxxxxxx> <20010716210029.I11938@xxxxxxxxxxxxx> <20010716101313.2DC3E965@xxxxxxxxxxxxxxxxx> <3B52C49F.9FE1F503@xxxxxxxxxxx> <15186.51514.66966.458597@xxxxxxxxxxxxxxxx> <3B5341BA.1F68F755@xxxxxxxxxxx> <15187.18225.196286.123754@xxxxxxxxxxxxxxxx> <3B534B74.BDE19961@xxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
> > For each open file you have:
> >
> >  struct file (96b)
> >  struct inode (460b)
> >  struct dentry (112b)
> >
> > at least. This totals to 668M of kernel memory, that is, unpageable.
> 
> As I said below, the NFS server should be a user-space daemon..

But the datastructures mentioned above would still be kernel-memory, so
that will not solve the problem.



-- 
Ragnar Kjorstad
Big Storage


<Prev in Thread] Current Thread [Next in Thread>