Re: sendfile(2) SF_NOPUSH flag proposal
From: Igor Sysoev (is_at_rambler-co.ru)
Date: 05/27/03
- Previous message: Igor Sysoev: "Re: sendfile(2) SF_NOPUSH flag proposal"
- In reply to: Terry Lambert: "Re: sendfile(2) SF_NOPUSH flag proposal"
- Next in thread: Marc Slemko: "Re: sendfile(2) SF_NOPUSH flag proposal"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 27 May 2003 22:38:55 +0400 (MSD) To: Terry Lambert <tlambert2@mindspring.com>
On Tue, 27 May 2003, Terry Lambert wrote:
> Why? Why not just fix the broken sendfile(2) implementation,
> instead?
Well, how ?
> So there's no barrier to you fixing this by either breaking
> up tcp_output() into two functions, or lazy-calling tcp_output(),
> instead of aggreesively calling it between headers and file
> data and file data and trailers in sendfile(2). Right? No
> API change necessary?
Did you look inside sendfile() implementation ?
There'are no tcp_output() calls at all. Header and trailer are written by
writev() and file pages are written by so->so_proto->pr_usrreqs->pru_send().
Igor Sysoev
http://sysoev.ru/en/
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Igor Sysoev: "Re: sendfile(2) SF_NOPUSH flag proposal"
- In reply to: Terry Lambert: "Re: sendfile(2) SF_NOPUSH flag proposal"
- Next in thread: Marc Slemko: "Re: sendfile(2) SF_NOPUSH flag proposal"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|