From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>,
nbd-general@lists.sourceforge.net, linux-newbie@vger.kernel.org
Subject: Re: [Qemu-devel] Transforming stdin and stdout pair into a socket
Date: Tue, 12 May 2009 00:07:23 +0100 [thread overview]
Message-ID: <200905120007.24881.paul@codesourcery.com> (raw)
In-Reply-To: <8e04b5820905110632q1a3b9ad4u49d4f3208d994755@mail.gmail.com>
> I've seen socat, and I could use it as you described. My only
> objection to this solution is that there is an unneeded process in the
> middle that just pipes data around...
>
> (Instead of socat, I think it would be more efficient to just write
> a simple application that uses the "new" Linux syscall "splice" that
> I've just found by mistake yesterday...)
In that case you need to fix socat to use splice() when available. I have a
hard time believing socat adds measurable overhead, especially if you're
already tunnelling over ssh.
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
WARNING: multiple messages have this Message-ID (diff)
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: nbd-general@lists.sourceforge.net, "Ciprian Dorin,
Craciun" <ciprian.craciun@gmail.com>,
linux-newbie@vger.kernel.org
Subject: Re: [Qemu-devel] Transforming stdin and stdout pair into a socket
Date: Tue, 12 May 2009 00:07:23 +0100 [thread overview]
Message-ID: <200905120007.24881.paul@codesourcery.com> (raw)
In-Reply-To: <8e04b5820905110632q1a3b9ad4u49d4f3208d994755@mail.gmail.com>
> I've seen socat, and I could use it as you described. My only
> objection to this solution is that there is an unneeded process in the
> middle that just pipes data around...
>
> (Instead of socat, I think it would be more efficient to just write
> a simple application that uses the "new" Linux syscall "splice" that
> I've just found by mistake yesterday...)
In that case you need to fix socat to use splice() when available. I have a
hard time believing socat adds measurable overhead, especially if you're
already tunnelling over ssh.
Paul
next prev parent reply other threads:[~2009-05-11 23:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 18:19 Transforming stdin and stdout pair into a socket Ciprian Dorin, Craciun
2009-05-10 18:19 ` [Qemu-devel] " Ciprian Dorin, Craciun
2009-05-11 8:03 ` [Nbd] " Laurent Vivier
2009-05-11 8:03 ` [Qemu-devel] " Laurent Vivier
2009-05-11 13:28 ` Ciprian Dorin, Craciun
2009-05-11 13:28 ` [Qemu-devel] Re: [Nbd] " Ciprian Dorin, Craciun
2009-05-11 12:02 ` [Qemu-devel] " Anthony Liguori
2009-05-11 12:02 ` Anthony Liguori
2009-05-11 13:32 ` Ciprian Dorin, Craciun
2009-05-11 13:32 ` Ciprian Dorin, Craciun
[not found] ` <8e04b5820905110632q1a3b9ad4u49d4f3208d994755-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-11 19:31 ` Wouter Verhelst
2009-05-11 19:31 ` [Nbd] " Wouter Verhelst
2009-05-11 23:07 ` Paul Brook [this message]
2009-05-11 23:07 ` Paul Brook
2009-05-12 2:24 ` Anthony Liguori
2009-05-12 2:24 ` Anthony Liguori
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=200905120007.24881.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=anthony@codemonkey.ws \
--cc=ciprian.craciun@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.