Re: sendto syscall is slow
Martin Devera (firstname.lastname@example.org)
Tue, 16 Oct 2001 15:56:11 +0200 (CEST)
> > i'm doing new qos discipline developement and use own
> > mesurment tool. It simply uses PF_PACKET and then
> > doing sendto/recv simulating various flows.
> > (I use both lo and eth0 where I short-connected RX-TX
> > pins in single ethcard)
> > I can't get beyond 25 000 packets per second. gprof:
> > Each sample counts as 0.01 seconds.
> > % cumulative self self total
> > time seconds seconds calls ms/call ms/call name
> > 35.67 5.39 5.39 498750 0.01 0.01 sendto
> > 26.67 9.42 4.03 1000826 0.00 0.00 poll
> > 19.06 12.30 2.88 498750 0.01 0.01 recv
> Increase the HZ constant in the kernel, which is determining the
> sceduler frequency, which is apparently due to BH handling acting
> as a low-pass filder for your siganls here. However please
> beware of many possible sideffects this may have on your system.
I did. The no of packets decreased:
37.40 6.63 6.63 439050 0.02 0.02 sendto
25.66 11.19 4.55 881028 0.01 0.01 poll
20.19 14.77 3.58 439050 0.01 0.01 recv
Not it is about 23 000/sec probably due to higher system overhead.
I don't think it could affect this case because recieve queue is
drained from softirq which is run when syscall returns to userspace.
So that is should not be bound to scheculer timing (as I both send
and recieve from single process).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/