[lkml]   [2008]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: request->ioprio
    On Wednesday 13 August 2008 17:06:03 Fernando Luis Vázquez Cao wrote:
    > Besides, I guess that accessing the io context information (such as
    > ioprio) of a request through elevator-specific private structures is not
    > something we want virtio_blk (or future users) to do.

    The only semantic I assumed was "higher is better". The server (ie. host) can
    really only use the information to schedule between I/Os for that particular
    guest anyway.

    But it sounds like I should be passing "0" in there unconditionally until the
    kernel semantics are sorted out and I can do something more intelligent? I
    haven't checked, but I assume that's actually what's happening at the moment
    (the field is zero)?

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2008-08-14 06:19    [W:0.024 / U:129.460 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site