From owner-freebsd-current Mon Feb 15 11:44:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20906 for freebsd-current-outgoing; Mon, 15 Feb 1999 11:44:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA20884 for ; Mon, 15 Feb 1999 11:44:17 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <54582(1)>; Mon, 15 Feb 1999 11:44:09 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Mon, 15 Feb 1999 11:43:56 -0800 To: Matthew Dillon cc: Bruce Evans , freebsd-current@FreeBSD.ORG Subject: Re: Weird piecemeal reads over socketpair() pipe breaks up small writes into even smaller reads. In-reply-to: Your message of "Mon, 15 Feb 99 10:58:19 PST." <199902151858.KAA18526@apollo.backplane.com> Date: Mon, 15 Feb 1999 11:43:46 PST From: Bill Fenner Message-Id: <99Feb15.114356pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isn't it easier to reclassify the bug as "uipc_send() wakes up the reader before it's done appending the data from a write() to the socket buffer" and use my patch? I don't think it makes sense for uipc_send() to depend on sorwakeup() not actually waking up anyone in certain situations. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message