James Carlson wrote: > Roland Mainz writes: > > Well, it would still be _nice_ to have either |sendfile()| support for > > all types of sockets and pipes in both directions to be consistent. The > > current behaviour of Solaris 11/B37 was the reason that we dropped the > > idea of using |sendfile()| for the /usr/bin/cat builtin in ksh93's > > libcmd (the same works Ok on Linux and most other platforms which have > > IPv6+|sendfile()|-support). > > > > Maybe a solution is to implement |sendfile()| in the kernel using a > > generic kernel copysendfiledata() loop if special |sendfile()| is > > missing for that type of socket/pipe... > > Perhaps, but I see that as rather separate from the underlying issue > that the original poster has.
My comment was more about that high-level libraries and applications can run into this problem without a good way to recover from the issue. Originally we looked at using |sendfile()| for ksh93's libcmd "cat" builtin but the lack of consistency on Solaris would require too many exception and compliciated error handling (the code worked on Linux but such a feature cannot be used on Solaris right now and therefore we stopped at that point). > In other words, even if we did have a > completely flexible any-to-any implementation of sendfile(), it's not > clear that it's really the right answer for the application he has. > It might help, but it seems a bit hackish to me. Right... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ networking-discuss mailing list [email protected]
