From: Daniel Drake <ddrake@brontes3d.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: splice blocks indefinitely when len > 64k?
Date: Mon, 30 Oct 2006 14:32:54 -0500 [thread overview]
Message-ID: <1162236774.7280.38.camel@systems03.lan.brontes3d.com> (raw)
In-Reply-To: <45464E67.7030004@cfl.rr.com>
On Mon, 2006-10-30 at 14:11 -0500, Phillip Susi wrote:
> While it should not simply hang, the splice size needs to be an even
> multiple of the page size.
I don't think that is true, at least on this level. Firstly, splice-cp
does this:
#define BS SPLICE_SIZE
int this_len = min((off_t) BS, sb.st_size);
int ret = splice(in_fd, NULL, pfds[1], NULL, this_len, 0);
No considerations are made regarding page size.
Secondly, the problem still exists when I increase SPLICE_SIZE to
(128*1024)
Daniel
> Daniel Drake wrote:
> > Hi,
> >
> > I'm experimenting with splice and have run into some unusual behaviour.
> >
> > I am using the utilities in git://brick.kernel.dk/data/git/splice.git
> >
> > In splice.h, when changing SPLICE_SIZE from:
> >
> > #define SPLICE_SIZE (64*1024)
> >
> > to
> >
> > #define SPLICE_SIZE ((64*1024)+1)
> >
> > splice-cp hangs indefinitely when copying files sized 65537 bytes or
> > more. It hangs on the first splice() call.
> >
> > Is this a bug? I'd like to be able to copy much more than 64kb on a
> > single splice call.
> >
> > Thanks!
> > Daniel
>
next prev parent reply other threads:[~2006-10-30 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 16:39 Daniel Drake
2006-10-30 19:11 ` Phillip Susi
2006-10-30 19:32 ` Daniel Drake [this message]
2006-10-30 19:55 ` Jens Axboe
2006-10-30 19:54 ` Jens Axboe
2006-10-30 21:08 ` Stephen Hemminger
2006-10-31 7:27 ` Jens Axboe
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=1162236774.7280.38.camel@systems03.lan.brontes3d.com \
--to=ddrake@brontes3d.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
/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