Skip to content
Snippets Groups Projects
  1. Jun 07, 2017
  2. May 24, 2017
  3. Mar 26, 2017
  4. Oct 08, 2016
  5. Aug 22, 2016
  6. May 27, 2016
  7. Dec 13, 2015
  8. Oct 30, 2015
  9. Aug 18, 2015
  10. May 30, 2015
  11. Apr 09, 2015
  12. Jan 04, 2015
  13. Dec 28, 2014
    • Andreas Dilger's avatar
      LU-6068 misc: update Intel copyright messages 2014 · 2b294992
      Andreas Dilger authored
      
      Update the copyright messages for changes made in 2014.
      
      In some cases, changes made in 2013 did not generate an updated
      copyright message, so these files are updated accordingly.  In some
      cases there were no licenses on newly-added files, so add them (either
      with new copyrights, or including copyrights from the source files).
      
      Some types of changes that are not actually changing the code
      (e.g. whitespace, mass changes to add or remote prefixes, patches
      updating the copyright messages, patch reversions and the reverted
      patch, patches that only delete code, etc.) have been excluded.
      
      The updatecw.sh script was updated to fix a number of problems:
      - it now handles comments in nroff (man page) files properly
      - remove need to handle non-Intel copyrights specially
      - allow subdirectory to be specified on command-line
      - improve script debugging when running with "sh -vx"
      - print patches changing the most files, to catch mass replacements
      
      There are still a few cases that need to be fixed up by hand (e.g.
      files split up and "git log --follow" can't find the original).
      
      Signed-off-by: default avatarAndreas Dilger <andreas.dilger@intel.com>
      Change-Id: Ib4875400a4908dc79ddc8b82ab0fe3ee903ebbe5
      Reviewed-on: http://review.whamcloud.com/13174
      
      
      Tested-by: Jenkins
      Tested-by: default avatarMaloo <hpdd-maloo@intel.com>
      Reviewed-by: default avatarOleg Drokin <oleg.drokin@intel.com>
      2b294992
  14. Nov 20, 2014
  15. Oct 05, 2014
  16. Sep 06, 2014
  17. Jul 15, 2014
  18. Jun 16, 2014
  19. Oct 25, 2013
  20. Sep 25, 2013
  21. Sep 18, 2013
  22. Sep 12, 2013
  23. Aug 20, 2013
  24. Jul 16, 2013
  25. May 31, 2013
  26. May 24, 2013
  27. May 02, 2013
  28. Apr 10, 2013
  29. Jan 08, 2013
  30. Sep 29, 2012
    • Alex Zhuravlev's avatar
      LU-1303 mds: integration lod/osp into the stack · 5165cdd4
      Alex Zhuravlev authored
      
       - config handler recognizes MDS config and replace LOV/OSC devices
         with LOD/OSP
      
       - the devices in MDS stack are setup from bottom to top using
         obd_connect() namely MDT->MDD->LOD->OSD, when new OSPs arrive,
         they connect to the OSD and LOD connects to every OSP). all the
         devices are referenced by exports, preventing them from early
         release.
      
       - once the whole configuration is processed, prepare() method of the
         top device is called, that in turn call ->prepare() down through
         the stack, etc. at this point the stack is considered ready to
         access storage, start recovery and do regular processing.
      
       - at umount ->ldo_process_config(LCFG_CLEANUP) is called down through
         the stack asking devices to release the resources (like objects
         referenced for internal purposes), then the series of calls to
         obd_disconnect()'s starting from the top MDT causes all the devices
         to become unreferenced and subject to release by zombie thread.
      
       - obd_notify() mechanism is not used by MDT/MDD/LOD/OSD, it's still
         used by OSP to be aware of current state:
      
            - to learn when the first connection to OST happens and let
              clients to connect to MDS, MDS uses obd_health_check() and
              caches positive result.
      
            - during object creation LOD uses dt_statfs() and data returned
              by OSP tells LOD whether specific OST active/inactive, space
              available, number of precreated objects, etc.
      
       - LOD takes care of striping: it maintains the list of available OST
         represented locally by OSP devices. on create, LOD finds suitable
         OSPs, create objects by means of OSD API and stores striping info
         into a local object. similarly LOD handles object destroy and
         UID/GID changes: load striping and execute on them.
      
       - llog is used by OSP as a local library, cookies are not visible out
         side of OSP. thus neither MDT nor MDD needs to care about cookies,
         prepare buffers. MDD doesn't need to send RPCs to destroy objects
         on behalf of evicted clients. all is hidden behind OSP's object
         destroy method.
      
       - OSP generates llog records for OST object being destroyed and, once
         corresponded local transaction is committed, send OST_DESTROY RPC.
         once OST_DESTROY is reported to be committed, corresponded llog
         record is cancelled.
      
       - the same logic is used for UID/GID changes.
      
      Signed-off-by: default avatarAlex Zhuravlev <alexey.zhuravlev@intel.com>
      Change-Id: Ifb282ace94f583ffa86020b763f22922e5d0b032
      Reviewed-on: http://review.whamcloud.com/4087
      
      
      Reviewed-by: default avatarAndreas Dilger <adilger@whamcloud.com>
      Tested-by: Hudson
      Tested-by: default avatarMaloo <whamcloud.maloo@gmail.com>
      Reviewed-by: default avatarMike Pershin <tappro@whamcloud.com>
      5165cdd4
  31. Aug 23, 2012
  32. Aug 08, 2012
  33. Jun 01, 2012
  34. Apr 19, 2012
  35. Apr 06, 2012
  36. Mar 29, 2012
  37. Mar 14, 2012
Loading