netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Henrik Happe <hhh@imada.sdu.dk>
To: netdev@vger.kernel.org
Subject: Re: Netchannels: netchannel vs. socket. 2:0.
Date: Fri, 9 Jun 2006 01:00:24 +0200	[thread overview]
Message-ID: <200606090100.24827.hhh@imada.sdu.dk> (raw)
In-Reply-To: <20060608171555.GA10273@2ka.mipt.ru>

On Thursday 08 June 2006 19:15, you wrote:
> After some enhancements made for netchannel subsystem I'm pleased to
> announce, that netchannel subsystem outperforms existing layered design
> both in CPU usage and network speed.
> 
> Well, after such pretentious introduction I want to cool things down.
> CPU usage is about 1-2% less for netchannels and network performance is
> about 1-2 MB higher and sometimes exceeds 84 MB/sec which, I think, 
> is maximum for given network setup (e1000 receive, r8169 send, 1500 MTU).

I have followed your work closely and have wondered how it affects latency?
I have somewhat limited knowledge about TCP and how the kernel handles it, but 
I guess the path from NIC to userspace hasn't increased. What about syscall 
overhead caused by userspace TCP processing?

H³  


  parent reply	other threads:[~2006-06-08 23:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 17:15 Netchannels: netchannel vs. socket. 2:0 Evgeniy Polyakov
2006-06-08 17:40 ` Evgeniy Polyakov
2006-06-08 23:00 ` Hans Henrik Happe [this message]
2006-06-09  5:09   ` Evgeniy Polyakov
2006-06-13 17:33 ` Netchannels: alternative TCP/IP stack? Evgeniy Polyakov
2006-06-29  9:38   ` Netchannels: progress report Evgeniy Polyakov
2006-06-29 17:19     ` James Morris
2006-06-29 18:15       ` Evgeniy Polyakov
2006-07-10 13:23     ` Netchannels: progress report. Sending benchmark Evgeniy Polyakov
2006-07-10 13:32       ` Evgeniy Polyakov

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=200606090100.24827.hhh@imada.sdu.dk \
    --to=hhh@imada.sdu.dk \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).