Traffic Server
  1. Traffic Server
  2. TS-61

Multiple do_io_pread on a CacheVConnection

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.0.0
    • Fix Version/s: None
    • Component/s: Cache
    • Labels:
      None

      Description

      The current TS-46 patch includes do_io_pread support but allows only a single do_io_pread.
      In order to efficiently support range requests with multiple ranges it would be helpful to be able
      to do multiple do_io_pread's on a single open CacheVConnection.

      1. pread-2.patch
        9 kB
        John Plevyak

        Issue Links

          Activity

          Hide
          Alan M. Carroll added a comment -

          As part of the partial object caching work, I have implemented full multi-range support for user agent requests using mechanisms based on the partial object support logic.

          Show
          Alan M. Carroll added a comment - As part of the partial object caching work, I have implemented full multi-range support for user agent requests using mechanisms based on the partial object support logic.
          Hide
          Alan M. Carroll added a comment -

          I think I'll roll this in to the partial object caching.

          Show
          Alan M. Carroll added a comment - I think I'll roll this in to the partial object caching.
          Hide
          Alan M. Carroll added a comment -

          I'll look at it as part of my cache API work.

          I would note that using this for ranges would require additional work elsewhere so I would put this out at 6.0.0.

          Show
          Alan M. Carroll added a comment - I'll look at it as part of my cache API work. I would note that using this for ranges would require additional work elsewhere so I would put this out at 6.0.0.
          Hide
          Leif Hedstrom added a comment -

          John Plevyak and Alan M. Carroll Any ideas on what we should do with this? amc should we include the proposed patch? I'm assigning this to you, for a screening / decision, move it to "sometime" if this is not something we should work on.

          Show
          Leif Hedstrom added a comment - John Plevyak and Alan M. Carroll Any ideas on what we should do with this? amc should we include the proposed patch? I'm assigning this to you, for a screening / decision, move it to "sometime" if this is not something we should work on.
          Show
          Leif Hedstrom added a comment - Moving to 5.0.0 as per https://cwiki.apache.org/confluence/display/TS/New+Release+Processes
          Hide
          Leif Hedstrom added a comment -

          Moving to 3.3.2.

          Show
          Leif Hedstrom added a comment - Moving to 3.3.2.
          Hide
          Leif Hedstrom added a comment -

          Moving out to v3.3.0, move back to 3.1.4 if this will be work on soon.

          Show
          Leif Hedstrom added a comment - Moving out to v3.3.0, move back to 3.1.4 if this will be work on soon .
          Hide
          Leif Hedstrom added a comment -

          I'm moving all 3.1.2 bugs out to 3.1.3, and we can move some 3.1.1 bugs out to 3.1.2, to get some release action going.

          Show
          Leif Hedstrom added a comment - I'm moving all 3.1.2 bugs out to 3.1.3, and we can move some 3.1.1 bugs out to 3.1.2, to get some release action going.
          Hide
          John Plevyak added a comment -

          This patches do_io_pread to work with a simple smoke test (included). This
          is a preliminary patch. Your millage may vary.

          Show
          John Plevyak added a comment - This patches do_io_pread to work with a simple smoke test (included). This is a preliminary patch. Your millage may vary.

            People

            • Assignee:
              Alan M. Carroll
              Reporter:
              John Plevyak
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 48h
                48h
                Remaining:
                Remaining Estimate - 48h
                48h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Development