mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fabian Franz <FabianFranz@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Use zero-copy (aka pipe/splice) for skbuff to enhance socketpair performance?
Date: Sun, 24 Sep 2006 19:38:31 +0200	[thread overview]
Message-ID: <200609241938.38378.FabianFranz@gmx.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

Hi,

as far as I know pipe() is now much faster than socketpair(), because pipe() 
uses the zero-copy mechanism.

However there are numerous applications using socketpair() instead of two 
pipe()s, because they need exactly _one_ fd for read/write instead of 2.

Over 180 open unix domain sockets are on my system right now.

Many of this applications could gain a speedup if only they could change to a 
different system call like epipe().

epipe() would behave like socketpair(), but internally use two pipes (one for 
each direction).

It seems so easy to do, so I'm really wondering, why it hasn't been done, yet?

However new system calls always have the problem of portability. Though in 
this case an epipe -> socketpair fallback would work.

So perhaps a better idea would be to enhance skbuff to use the new zero-copy 
mechanism ... ?

The reason why I had the idea is that I had huge socketpair performance 
problems, but with an old 2.4.27 kernel and a custom kernel module:

Almost 1 sec of latency!

Changing the fds provided from userspace to pipe()s did result in good 
performance.

Might be a bug in my module though ...

cu

Fabian

PS: Please CC me as I'm not subscribed.

-- 
      *** Consulting - Training - Workshops - Troubleshooting ***
   @@@ LiveCDs (Knoppix), Debian, Remote Desktop Access (FreeNX) @@@

--- Fabian Franz --- www.fabian-franz.de --- consulting@fabian-franz.de

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2006-09-24 20:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200609241938.38378.FabianFranz@gmx.de \
    --to=fabianfranz@gmx.de \
    --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

all inboxes | Powered by JetHome®