Skip to main content

Browse the archive

Revision dc59250c6ebed099a9bc0a11298e2281dd896657 authored by Chuck Lever on 18 August 2005, 18:24:12 UTC, committed by Linus Torvalds on 18 August 2005, 19:53:57 UTC 
[PATCH] NFS: Introduce the use of inode->i_lock to protect fields in nfsi
 
Down the road we want to eliminate the use of the global kernel lock entirely
from the NFS client.  To do this, we need to protect the fields in the
nfs_inode structure adequately.  Start by serializing updates to the
"cache_validity" field.

Note this change addresses an SMP hang found by njw@osdl.org, where processes
deadlock because nfs_end_data_update and nfs_revalidate_mapping update the
"cache_validity" field without proper serialization.

Test plan:
 Millions of fsx ops on SMP clients.  Run Nick Wilson's breaknfs program on
 large SMP clients.

Signed-off-by: Chuck Lever <cel@netapp.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
1 parent 412d582
Raw File
mpc52xx.txt 
Linux 2.6.x on MPC52xx family
-----------------------------

For the latest info, go to http://www.246tNt.com/mpc52xx/
 
To compile/use :

  - U-Boot:
     # <edit Makefile to set ARCH=ppc & CROSS_COMPILE=... ( also EXTRAVERSION
        if you wish to ).
     # make lite5200_defconfig
     # make uImage
    
     then, on U-boot:
     => tftpboot 200000 uImage
     => tftpboot 400000 pRamdisk
     => bootm 200000 400000
    
  - DBug:
     # <edit Makefile to set ARCH=ppc & CROSS_COMPILE=... ( also EXTRAVERSION
        if you wish to ).
     # make lite5200_defconfig
     # cp your_initrd.gz arch/ppc/boot/images/ramdisk.image.gz
     # make zImage.initrd 
     # make 

     then in DBug:
     DBug> dn -i zImage.initrd.lite5200
     

Some remarks :
 - The port is named mpc52xxx, and config options are PPC_MPC52xx. The MGT5100
   is not supported, and I'm not sure anyone is interesting in working on it
   so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
   nothing to do with the MPC5200. I also included the 'MPC' for the same
   reason.
 - Of course, I inspired myself from the 2.4 port. If you think I forgot to
   mention you/your company in the copyright of some code, I'll correct it
   ASAP.
back to top