[lkml]   [2012]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v2 1/1] mmc: block: Add write packing control
    Hi,  [removing Jens and the documentation list, since now we're
    talking about the MMC side only]

    On Wed, Jul 18 2012, wrote:
    > Is there anything else that holds this patch from being pushed to mmc-next?

    Yes, I'm still uncomfortable with the write packing patchsets for a
    couple of reasons, and I suspect that the sum of those reasons means
    that we should probably plan on holding off merging it until after 3.6.

    Here are the open issues; please correct any misunderstandings:

    With Seungwon's patchset ("Support packed write command"):

    * I still don't have a good set of representative benchmarks showing
    what kind of performance changes come with this patchset. It seems
    like we've had a small amount of testing on one controller/eMMC part
    combo from Seungwon, and an entirely different test from Maya, and the
    results aren't documented fully anywhere to the level of describing
    what the hardware was, what the test was, and what the results were
    before and after the patchset.

    With the reads-during-writes regression:

    * Venkat still has open questions about the nature of the read
    regression, and thinks we should understand it with blktrace before
    trying to fix it. Maya has a theory about writes overwhelming reads,
    but Venkat doesn't understand why this would explain the observed
    bandwidth drop.

    With Maya's patchset ("write packing control"):

    * Venkat thinks that HPI should be used, and the number-of-requests
    metric is too coarse, and it doesn't let you disable packing at the
    right time, and you're essentially implementing a new I/O scheduler
    inside the MMC subsystem without understanding the root cause for
    why that's necessary.

    My sense is that there's no way we can solve all of these to
    satisfaction in the next week (which is when the merge window will
    open), but that by waiting a cycle we might come up with some good

    What do other people think? If you're excited about these patchsets,
    now would be a fine time to come forward with your benchmarking results
    and to help understand the reads-during-writes regression.


    - Chris.
    Chris Ball <> <>
    One Laptop Per Child

     \ /
      Last update: 2012-07-18 10:01    [W:0.023 / U:295.420 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site