| To: | Andrew Morton <andrewm@xxxxxxxxxx> |
|---|---|
| Subject: | Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN) |
| From: | Aaron Lehmann <aaronl@xxxxxxxxxxx> |
| Date: | Fri, 26 Jan 2001 22:20:03 -0800 |
| Cc: | lkml <linux-kernel@xxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx> |
| In-reply-to: | <3A726087.764CC02E@xxxxxxxxxx>; from andrewm@xxxxxxxxxx on Sat, Jan 27, 2001 at 04:45:43PM +1100 |
| References: | <3A726087.764CC02E@xxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.12i |
On Sat, Jan 27, 2001 at 04:45:43PM +1100, Andrew Morton wrote: > 2.4.1-pre10-vanilla, using read()/write(): 34.5% CPU > 2.4.1-pre10+zercopy, using read()/write(): 38.1% CPU Am I right to be bothered by this? The majority of Unix network traffic is handled with read()/write(). Why would zerocopy slow that down? If zerocopy is simply unoptimized, that's fine for now. But if the problem is inherent in the implementation or design, that might be a problem. Any patch which incurs a signifigant slowdown on traditional networking should be contraversial. Aaron Lehmann please ignore me if I don't know what I'm talking about. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | sendfile+zerocopy: fairly sexy (nothing to do with ECN), Andrew Morton |
|---|---|
| Next by Date: | Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN), Andrew Morton |
| Previous by Thread: | sendfile+zerocopy: fairly sexy (nothing to do with ECN), Andrew Morton |
| Next by Thread: | Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN), Andrew Morton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |