1. 26 3月, 2016 1 次提交
    • Y
      ceph: scattered page writeback · 5b64640c
      Yan, Zheng 提交于
      This patch makes ceph_writepages_start() try using single OSD request
      to write all dirty pages within a strip unit. When a nonconsecutive
      dirty page is found, ceph_writepages_start() tries starting a new write
      operation to existing OSD request. If it succeeds, it uses the new
      operation to writeback the dirty page.
      Signed-off-by: NYan, Zheng <zyan@redhat.com>
      5b64640c
  2. 05 3月, 2016 1 次提交
  3. 22 1月, 2016 3 次提交
  4. 07 11月, 2015 1 次提交
  5. 11 9月, 2015 1 次提交
  6. 09 9月, 2015 3 次提交
  7. 25 6月, 2015 7 次提交
  8. 22 4月, 2015 1 次提交
  9. 20 4月, 2015 1 次提交
  10. 12 4月, 2015 1 次提交
  11. 19 2月, 2015 1 次提交
  12. 11 2月, 2015 1 次提交
  13. 09 1月, 2015 1 次提交
  14. 18 12月, 2014 6 次提交
  15. 15 10月, 2014 1 次提交
    • C
      ceph: remove redundant code for max file size verification · a4483e8a
      Chao Yu 提交于
      Both ceph_update_writeable_page and ceph_setattr will verify file size
      with max size ceph supported.
      There are two caller for ceph_update_writeable_page, ceph_write_begin and
      ceph_page_mkwrite. For ceph_write_begin, we have already verified the size in
      generic_write_checks of ceph_write_iter; for ceph_page_mkwrite, we have no
      chance to change file size when mmap. Likewise we have already verified the size
      in inode_change_ok when we call ceph_setattr.
      So let's remove the redundant code for max file size verification.
      Signed-off-by: NChao Yu <chao2.yu@samsung.com>
      Reviewed-by: NYan, Zheng <zyan@redhat.com>
      a4483e8a
  16. 07 6月, 2014 1 次提交
  17. 06 6月, 2014 1 次提交
  18. 07 5月, 2014 1 次提交
  19. 29 1月, 2014 1 次提交
  20. 01 1月, 2014 2 次提交
  21. 14 12月, 2013 2 次提交
  22. 24 11月, 2013 1 次提交
  23. 07 9月, 2013 1 次提交
    • M
      ceph: page still marked private_2 · d4d3aa38
      Milosz Tanski 提交于
      Previous patch that allowed us to cleanup most of the issues with pages marked
      as private_2 when calling ceph_readpages. However, there seams to be a case in
      the error case clean up in start read that still trigers this from time to
      time. I've only seen this one a couple times.
      
      BUG: Bad page state in process petabucket  pfn:335b82
      page:ffffea000cd6e080 count:0 mapcount:0 mapping:          (null) index:0x0
      page flags: 0x200000000001000(private_2)
      Call Trace:
       [<ffffffff81563442>] dump_stack+0x46/0x58
       [<ffffffff8112c7f7>] bad_page+0xc7/0x120
       [<ffffffff8112cd9e>] free_pages_prepare+0x10e/0x120
       [<ffffffff8112e580>] free_hot_cold_page+0x40/0x160
       [<ffffffff81132427>] __put_single_page+0x27/0x30
       [<ffffffff81132d95>] put_page+0x25/0x40
       [<ffffffffa02cb409>] ceph_readpages+0x2e9/0x6f0 [ceph]
       [<ffffffff811313cf>] __do_page_cache_readahead+0x1af/0x260
      Signed-off-by: NMilosz Tanski <milosz@adfin.com>
      Signed-off-by: NSage Weil <sage@inktank.com>
      d4d3aa38