All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Daniel Drake <ddrake@brontes3d.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: splice blocks indefinitely when len > 64k?
Date: Mon, 30 Oct 2006 20:54:27 +0100	[thread overview]
Message-ID: <20061030195426.GO14055@kernel.dk> (raw)
In-Reply-To: <1162226390.7280.18.camel@systems03.lan.brontes3d.com>

On Mon, Oct 30 2006, 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.

You can't, internally splice is using a pipe which is currently confined
to 16 pages. The SPLICE_SIZE define isn't a suggestion in the code, it
reflects that. You could fix splice-cp to not stall on changing that,
however that still doesn't change the fact that you can only move chunks
of 64kb (on your arch) right now.

-- 
Jens Axboe


  parent reply	other threads:[~2006-10-30 19:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 16:39 splice blocks indefinitely when len > 64k? Daniel Drake
2006-10-30 19:11 ` Phillip Susi
2006-10-30 19:32   ` Daniel Drake
2006-10-30 19:55   ` Jens Axboe
2006-10-30 19:54 ` Jens Axboe [this message]
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=20061030195426.GO14055@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=ddrake@brontes3d.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 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.