On Thu, 24 Jan 2013 23:21:19 +0100 Roland Mainz wrote:
> On Thu, Jan 24, 2013 at 11:14 PM, Glenn Fowler <[email protected]> wrote:
> > I added a #define to avoid the collision
> Erm... how should a #define work in this case ? |splice()| is a libc
> _symbol_...
#include <header-that-has-splice-prototype.h>
#define splice splicef
static void splice(void) { }
> ... and there is still the open question in the original email
> above... basically "... can libast sfio+AST tee(1) benefit from
> Linux's |splice()| ..." (I'm not sure since there are usage
> limitations similar to Solaris |sendfile()|, e.g. " ... one of the
> descriptors must refer to a pipe ...") ?
I thought I answered this, maybe in another context, a while ago
maybe it just remained a thought ...
splice(2) would be a candidate for use in the sfmove() inner loop
and that would affect many ast command implementations
too bad that one of the fds *must* be a pipe
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
