10 Mar, 2011

1 commit

  • In contrast to SIOCOUTQ which returns the amount of data sent
    but not yet acknowledged plus data not yet sent this patch only
    returns the data not sent.

    For various methods of live streaming bitrate control it may
    be helpful to know how much data are in the tcp outqueue are
    not sent yet.

    Signed-off-by: Mario Schuknecht
    Signed-off-by: Steffen Sledz
    Signed-off-by: David S. Miller

    Mario Schuknecht
     

16 Feb, 2009

1 commit

  • User space can request hardware and/or software time stamping.
    Reporting of the result(s) via a new control message is enabled
    separately for each field in the message because some of the
    fields may require additional computation and thus cause overhead.
    User space can tell the different kinds of time stamps apart
    and choose what suits its needs.

    When a TX timestamp operation is requested, the TX skb will be cloned
    and the clone will be time stamped (in hardware or software) and added
    to the socket error queue of the skb, if the skb has a socket
    associated with it.

    The actual TX timestamp will reach userspace as a RX timestamp on the
    cloned packet. If timestamping is requested and no timestamping is
    done in the device driver (potentially this may use hardware
    timestamping), it will be done in software after the device's
    start_hard_xmit routine.

    Signed-off-by: Patrick Ohly
    Signed-off-by: David S. Miller

    Patrick Ohly
     

03 Dec, 2006

1 commit


06 May, 2005

1 commit


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds