[lkml]   [2001]   [Oct]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: sendto syscall is slow
    > Do you have the same profile for sendto when Rx/Tx isn't short 
    > connected ?

    I have not. I have only one computer and one 100Mbit eth card
    at home. But I've got the same results when I used loopback
    But without loopback wires it goes like this:
    41.03 4.34 4.34 478200 0.01 0.01 sendto
    29.52 7.46 3.12 481389 0.01 0.01 poll
    14.70 9.02 1.55 478200 0.00 0.00 setsockopt

    > You may consider polling for Tx/Rx completion in the Tx path at the
    > driver level. If your cpu isn't too much powered it will make
    > a difference.

    Are you speaking about rewriting nic driver ? Like try to drain
    waiting packet from nic's memory while enqueuing new one ?

    IMHO the bottleneck will be probably in send syscall (probably
    syscall overhead).
    I'm thinking about hack which will allow me to send() large
    buffer and kernel code will break it into smaller ones and
    device_queue_xmit them at once.


    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: 2005-03-22 13:08    [W:0.025 / U:8.364 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site