Re: Possible problem with zero-copy TCP and sendfile()

2001-04-17 Thread Jesse S Sipprell
On Tue, Apr 17, 2001 at 01:23:07PM -0700, David S. Miller wrote: > One more subtle note, for the case of error handling. There is a > change to sendfile() in the zerocopy patches which causes sendfile() > to act more like sendmsg() when errors occur. How is this likely to affect applications?

Re: Possible problem with zero-copy TCP and sendfile()

2001-04-17 Thread Jesse S Sipprell
On Tue, Apr 17, 2001 at 06:15:24PM +0200, Jan Kasprzak wrote: > Alan Cox wrote: > : > : but once a fixed BIOS is out for your board that would be a good first step. > : > : If it still does it then, its worth digging for kernel naughties > : > : > : > I don't think I have 686b southbridge. I

Re: Possible problem with zero-copy TCP and sendfile()

2001-04-17 Thread Jesse S Sipprell
On Tue, Apr 17, 2001 at 06:15:24PM +0200, Jan Kasprzak wrote: Alan Cox wrote: : : but once a fixed BIOS is out for your board that would be a good first step. : : If it still does it then, its worth digging for kernel naughties : : :I don't think I have 686b southbridge. I have 686

Re: Possible problem with zero-copy TCP and sendfile()

2001-04-17 Thread Jesse S Sipprell
On Tue, Apr 17, 2001 at 01:23:07PM -0700, David S. Miller wrote: One more subtle note, for the case of error handling. There is a change to sendfile() in the zerocopy patches which causes sendfile() to act more like sendmsg() when errors occur. How is this likely to affect applications?