From: David Miller <davem@davemloft.net>
To: jaschut@sandia.gov
Cc: linux-kernel@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: splice/vmsplice performance test results
Date: Thu, 16 Nov 2006 15:52:24 -0500 (EST) [thread overview]
Message-ID: <20061116.155224.08323028.davem@davemloft.net> (raw)
In-Reply-To: <1163700539.2672.14.camel@sale659.sandia.gov>
From: "Jim Schutt" <jaschut@sandia.gov>
Date: Thu, 16 Nov 2006 11:08:59 -0700
> Or is read+write really the fastest way to get data off a
> socket and into a file?
There is still no explicit TCP support for splice/vmsplice so things
get copied around and most of the other advantaves of splice/vmplice
aren't obtained either. So perhaps that explains your numbers.
Jens Axboe tries to get things working, and others have looked into it
too, but adding TCP support is hard and for several reasons folks like
Alexey Kuznetsov and Evgeniy Polyakov believe that sys_receivefile()
is an interface much better suited for TCP receive.
splice/vmsplice has a lot of state connected to a transaction, and
perhaps that is part of why Evgeniy and Alexey have trouble wrapping
their brains around an efficient implementation.
next prev parent reply other threads:[~2006-11-16 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 18:08 Jim Schutt
2006-11-16 20:25 ` Jens Axboe
2006-11-16 21:24 ` Jim Schutt
2006-11-17 17:21 ` Jim Schutt
2006-11-20 7:59 ` Jens Axboe
2006-11-20 8:24 ` Jens Axboe
2006-11-20 15:49 ` Jim Schutt
2006-11-21 13:54 ` Jens Axboe
2006-11-21 19:17 ` Jim Schutt
2006-11-22 8:57 ` Jens Axboe
2006-11-22 22:35 ` Jim Schutt
2006-11-23 11:24 ` Jens Axboe
2006-11-27 20:57 ` Jim Schutt
2006-11-16 20:52 ` David Miller [this message]
2006-11-16 21:21 ` Jens Axboe
2006-11-16 21:27 ` David Miller
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=20061116.155224.08323028.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jaschut@sandia.gov \
--cc=jens.axboe@oracle.com \
--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