From: Jens Axboe <jens.axboe@oracle.com>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Remi Machet <rmachet@slac.stanford.edu>,
Linux Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: SPLICE_F_MOVE
Date: Tue, 23 Sep 2008 13:59:20 +0200 [thread overview]
Message-ID: <20080923115920.GZ26460@kernel.dk> (raw)
In-Reply-To: <517f3f820809230456r66fa68dcw2362b214ca1de5f6@mail.gmail.com>
On Tue, Sep 23 2008, Michael Kerrisk wrote:
> [CC+=Jens, who should be able to help]
>
> On 9/23/08, Remi Machet <rmachet@slac.stanford.edu> wrote:
> > Hi,
> >
> > Does anyone know if SPLICE_F_MOVE is obsolete or still in use ?
> >
> > The documentation says that the flag should be used to tell splice not
> > to copy the data when moving data to/from a pipe, but I cannot find
> > anywhere in the kernel where this flag is being used or checked for.
It's not currently used, it got yanked and is waiting for a replacement
implementation.
--
Jens Axboe
prev parent reply other threads:[~2008-09-23 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 23:25 SPLICE_F_MOVE Remi Machet
2008-09-23 11:56 ` SPLICE_F_MOVE Michael Kerrisk
2008-09-23 11:59 ` Jens Axboe [this message]
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=20080923115920.GZ26460@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=rmachet@slac.stanford.edu \
/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