1. 14 Jul, 2008 1 commit
  2. 24 Jan, 2008 4 commits
  3. 22 Aug, 2007 1 commit
  4. 10 Aug, 2007 1 commit
  5. 10 May, 2007 1 commit
  6. 12 Feb, 2007 1 commit
  7. 05 Feb, 2007 1 commit
  8. 08 Dec, 2006 1 commit
  9. 01 Oct, 2006 1 commit
  10. 27 Sep, 2006 2 commits
    • Theodore Ts'o's avatar
      [PATCH] inode-diet: Eliminate i_blksize from the inode structure · ba52de12
      Theodore Ts'o authored
      
      
      This eliminates the i_blksize field from struct inode.  Filesystems that want
      to provide a per-inode st_blksize can do so by providing their own getattr
      routine instead of using the generic_fillattr() function.
      
      Note that some filesystems were providing pretty much random (and incorrect)
      values for i_blksize.
      
      [bunk@stusta.de: cleanup]
      [akpm@osdl.org: generic_fillattr() fix]
      Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
      Signed-off-by: default avatarAdrian Bunk <bunk@stusta.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      ba52de12
    • Theodore Ts'o's avatar
      [PATCH] inode_diet: Replace inode.u.generic_ip with inode.i_private · 8e18e294
      Theodore Ts'o authored
      
      
      The following patches reduce the size of the VFS inode structure by 28 bytes
      on a UP x86.  (It would be more on an x86_64 system).  This is a 10% reduction
      in the inode size on a UP kernel that is configured in a production mode
      (i.e., with no spinlock or other debugging functions enabled; if you want to
      save memory taken up by in-core inodes, the first thing you should do is
      disable the debugging options; they are responsible for a huge amount of bloat
      in the VFS inode structure).
      
      This patch:
      
      The filesystem or device-specific pointer in the inode is inside a union,
      which is pretty pointless given that all 30+ users of this field have been
      using the void pointer.  Get rid of the union and rename it to i_private, with
      a comment to explain who is allowed to use the void pointer.  This is just a
      cleanup, but it allows us to reuse the union 'u' for something something where
      the union will actually be used.
      
      [judith@osdl.org: powerpc build fix]
      Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
      Signed-off-by: default avatarJudith Lebzelter <judith@osdl.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      8e18e294
  11. 20 Sep, 2006 2 commits
  12. 23 Jun, 2006 2 commits
    • Andrew Morton's avatar
      [PATCH] s390_hypfs filesystem: get_sb_single() fix · a5cf4b9a
      Andrew Morton authored
      
      
      Update hypfs for dhowells API changes.
      
      Cc: Pekka Enberg <penberg@cs.helsinki.fi>
      Cc: Ingo Oeser <ioe-lkml@rameria.de>
      Cc: Joern Engel <joern@wohnheim.fh-wedel.de>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Michael Holzheu <holzheu@de.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      a5cf4b9a
    • Michael Holzheu's avatar
      [PATCH] s390_hypfs filesystem · 24bbb1fa
      Michael Holzheu authored
      
      
      On zSeries machines there exists an interface which allows the operating
      system to retrieve LPAR hypervisor accounting data.  For example, it is
      possible to get usage data for physical and virtual cpus.  In order to
      provide this information to user space programs, I implemented a new
      virtual Linux file system named 's390_hypfs' using the Linux 2.6 libfs
      framework.  The name 's390_hypfs' stands for 'S390 Hypervisor Filesystem'.
      All the accounting information is put into different virtual files which
      can be accessed from user space.  All data is represented as ASCII strings.
      
      When the file system is mounted the accounting information is retrieved and
      a file system tree is created with the attribute files containing the cpu
      information.  The content of the files remains unchanged until a new update
      is made.  An update can be triggered from user space through writing
      'something' into a special purpose update file.
      
      We create the following directory structure:
      
      <mount-point>/
              update
              cpus/
                      <cpu-id>
                              type
                              mgmtime
                      <cpu-id>
                              ...
              hyp/
                      type
              systems/
                      <lpar-name>
                              cpus/
                                      <cpu-id>
                                              type
                                              mgmtime
                                              cputime
                                              onlinetime
                                      <cpu-id>
                                              ...
                      <lpar-name>
                              cpus/
                                      ...
      
      - update: File to trigger update
      - cpus/: Directory for all physical cpus
      - cpus/<cpu-id>/: Directory for one physical cpu.
      - cpus/<cpu-id>/type: Type name of physical zSeries cpu.
      - cpus/<cpu-id>/mgmtime: Physical-LPAR-management time in microseconds.
      - hyp/: Directory for hypervisor information
      - hyp/type: Typ of hypervisor (currently only 'LPAR Hypervisor')
      - systems/: Directory for all LPARs
      - systems/<lpar-name>/: Directory for one LPAR.
      - systems/<lpar-name>/cpus/<cpu-id>/: Directory for the virtual cpus
      - systems/<lpar-name>/cpus/<cpu-id>/type: Typ of cpu.
      - systems/<lpar-name>/cpus/<cpu-id>/mgmtime:
      Accumulated number of microseconds during which a physical
      CPU was assigned to the logical cpu and the cpu time was
      consumed by the hypervisor and was not provided to
      the LPAR (LPAR overhead).
      
      - systems/<lpar-name>/cpus/<cpu-id>/cputime:
      Accumulated number of microseconds during which a physical CPU
      was assigned to the logical cpu and the cpu time was consumed
      by the LPAR.
      
      - systems/<lpar-name>/cpus/<cpu-id>/onlinetime:
      Accumulated number of microseconds during which the logical CPU
      has been online.
      
      As mount point for the filesystem /sys/hypervisor/s390 is created.
      
      The update process is triggered when writing 'something' into the
      'update' file at the top level hypfs directory. You can do this e.g.
      with 'echo 1 > update'. During the update the whole directory structure
      is deleted and built up again.
      
      Cc: Pekka Enberg <penberg@cs.helsinki.fi>
      Cc: Ingo Oeser <ioe-lkml@rameria.de>
      Cc: Joern Engel <joern@wohnheim.fh-wedel.de>
      Acked-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: default avatarMichael Holzheu <holzheu@de.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      24bbb1fa