xfs-masters
[Top] [All Lists]

[xfs-masters] Re: [2.6 patch] i386: always use 4k stacks

To: Adrian Bunk <bunk@xxxxxxxxx>
Subject: [xfs-masters] Re: [2.6 patch] i386: always use 4k stacks
From: Neil Brown <neilb@xxxxxxx>
Date: Mon, 19 Dec 2005 11:45:24 +1100
Cc: Dave Jones <davej@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, arjan@xxxxxxxxxxxxx, xfs-masters@xxxxxxxxxxx, nathans@xxxxxxx
In-reply-to: message from Adrian Bunk on Friday December 16
References: <20051215212447.GR23349@xxxxxxxxx> <20051215140013.7d4ffd5b.akpm@xxxxxxxx> <20051215223000.GU23349@xxxxxxxxx> <20051215231538.GF3419@xxxxxxxxxx> <20051216004740.GV23349@xxxxxxxxx> <20051216005056.GG3419@xxxxxxxxxx> <17314.11514.650036.686071@xxxxxxxxxxxxxxx> <20051216121805.GX23349@xxxxxxxxx>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
On Friday December 16, bunk@xxxxxxxxx wrote:
> 
> The nfsd code uses inline in too many places.

Does it?
Most of the uses are either
 - truly tiny bits of code
 - code that is used only once which, as you as, will not currently 
   be auto-inlined on i386, so we do it by hand.

An exception is some of the xdr code.
If I 
  #define inline
in nfs3xdr.c, the nfsd.o changes from 
   text    data     bss     dec     hex filename
  76132    3464    2408   82004   14054 ../mm-i386/fs/nfsd/nfsd.o
to
   text    data     bss     dec     hex filename
  72452    3464    2408   78324   131f4 ../mm-i386/fs/nfsd/nfsd.o
which is probably a win.

Is that what you were referring to?

> 
> If this struct is really a problem (which I doubt considering it's 
> size), I'd prefer it being kmalloc'ed.

It's hard to *know* if it is a problem, but I am conscious that nfsd
adds measurably to stack depth for filesystem paths, and probably
isn't measured nearly as often.
It's true that 50 bytes out of 4K isn't a lot, but wastage that can be
avoided, should be avoided.

NeilBrown


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