From: Francois Romieu <romieu@cogenit.fr>
To: Martin Devera <devik@cdi.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sendto syscall is slow
Date: Tue, 16 Oct 2001 17:59:08 +0200 [thread overview]
Message-ID: <20011016175908.A2258@se1.cogenit.fr> (raw)
In-Reply-To: <Pine.LNX.4.33.0110151105400.22170-100000@shell1.aracnet.com> <Pine.LNX.4.10.10110161438140.13894-100000@luxik.cdi.cz>
In-Reply-To: <Pine.LNX.4.10.10110161438140.13894-100000@luxik.cdi.cz>; from devik@cdi.cz on Tue, Oct 16, 2001 at 02:45:47PM +0200
Martin Devera <devik@cdi.cz> :
[sendto/recv profile]
> Is there any faster way to force raw packets to kernel ? I need
> to push qos discipline to its edge but I can't because send
> syscall is bottleneck.
> Is it possible to tx multiple packets in sinhle call or should
> I extend kernel myself for this testing purpose ?
Do you have the same profile for sendto when Rx/Tx isn't short
connected ?
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.
--
Ueimor
next prev parent reply other threads:[~2001-10-16 15:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 18:26 2.4.13pre2aa1 Andrea Arcangeli
2001-10-15 17:31 ` new VM: what is classzone ? Martin Devera
2001-10-15 18:11 ` How many versions of VM are there? M. Edward (Ed) Borasky
2001-10-15 20:58 ` Slo Mo Snail
2001-10-15 21:15 ` Mike Fedyk
2001-10-15 22:24 ` Tim Moore
2001-10-15 22:29 ` Mike Fedyk
2001-10-15 22:41 ` Gerhard Mack
2001-10-16 11:23 ` snpe
2001-10-16 10:39 ` Very old kernel Kirill Ratkin
2001-10-16 13:30 ` David Weinehall
2001-10-16 12:45 ` sendto syscall is slow Martin Devera
2001-10-16 13:00 ` Martin Dalecki
2001-10-16 13:56 ` Martin Devera
2001-10-16 15:59 ` Francois Romieu [this message]
2001-10-16 16:08 ` Ref: zerocopy +netfilter performance problem Ravi Chamarti
2001-10-16 16:15 ` sendto syscall is slow Martin Devera
2001-10-16 17:02 ` Francois Romieu
2001-10-16 17:11 ` Martin Devera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011016175908.A2258@se1.cogenit.fr \
--to=romieu@cogenit.fr \
--cc=devik@cdi.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome