1. 16 1月, 2017 15 次提交
  2. 07 12月, 2016 1 次提交
    • E
      qapi: Document introduction of gluster's 'debug' option · 4230e5d1
      Eric Blake 提交于
      We intentionally renamed 'debug-level' to 'debug' in the QMP
      schema for 'blockdev-add' related to gluster, in order to
      match the command line (commit 1a417e46).  However, since
      'debug-level' was visible in 2.7, that means that we should
      document that 'debug' was not available until 2.8.
      
      The change was intentional because 'blockdev-add' itself
      underwent incompatible changes (such as commit 0153d2f5) for
      the same release; our intent is that after 2.8, these
      interfaces will now be stable.  [In hindsight, we should have
      used the name x-blockdev-add when we first introduced it]
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Message-id: 20161206182020.25736-1-eblake@redhat.com
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      4230e5d1
  3. 06 12月, 2016 7 次提交
  4. 15 11月, 2016 1 次提交
    • M
      block/curl: Drop TFTP "support" · 23dce387
      Max Reitz 提交于
      Because TFTP does not support byte ranges, it was never usable with our
      curl block driver. Since apparently nobody has ever complained loudly
      enough for someone to take care of the issue until now, it seems
      reasonable to assume that nobody has ever actually used it.
      
      Therefore, it should be safe to just drop it from curl's protocol list.
      
      [Jeff Cody: Below is additional summary pulled, with some rewording,
                  from followup emails between Max and Markus, to explain what
                  worked and what didn't]
      
      TFTP would sometimes work, to a limited extent, for images <= the curl
      "readahead" size, so long as reads started at offset zero.  By default,
      that readahead size is 256KB.
      
      Reads starting at a non-zero offset would also have returned data from a
      zero offset.  It can become more complicated still, with mixed reads at
      zero offset and non-zero offsets, due to data buffering.
      
      In short, TFTP could only have worked before in very specific scenarios
      with unrealistic expectations and constraints.
      Signed-off-by: NMax Reitz <mreitz@redhat.com>
      Reviewed-by: NKevin Wolf <kwolf@redhat.com>
      Reviewed-by: NJeff Cody <jcody@redhat.com>
      Message-id: 20161102175539.4375-4-mreitz@redhat.com
      Signed-off-by: NJeff Cody <jcody@redhat.com>
      23dce387
  5. 01 11月, 2016 1 次提交
  6. 31 10月, 2016 6 次提交
  7. 28 10月, 2016 1 次提交
  8. 24 10月, 2016 2 次提交
  9. 08 10月, 2016 1 次提交
  10. 07 10月, 2016 1 次提交
  11. 29 9月, 2016 2 次提交
  12. 23 9月, 2016 2 次提交