| To: | davem@xxxxxxxxxx ("David S. Miller") |
|---|---|
| Subject: | Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1 |
| From: | Christoph Hellwig <hch@xxxxxxxxxx> |
| Date: | Mon, 8 Jan 2001 11:39:15 +0100 |
| Cc: | netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <200101080124.RAA08134@xxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | tin/1.4.1-19991201 ("Polish") (UNIX) (Linux/2.2.14 (i686)) |
In article <200101080124.RAA08134@xxxxxxxxxxxxxxx> you wrote:
> I've put a patch up for testing on the kernel.org mirrors:
>
> /pub/linux/kernel/people/davem/zerocopy-2.4.0-1.diff.gz
>
> It provides a framework for zerocopy transmits and delayed
> receive fragment coalescing. TUX-1.01 uses this framework.
Hi Dave,
don't you think the writepage file operation is rather hackish?
I'd much prefer Ben La Haise's rw_kiovec [1] operation, it is more
generic (supports read and write) and should be easily usable for
zerocopy networking with plain old write (using map_user_kio).
Besides that the FS crew thinks it should go in soon because of
aio anyway...
Christoph
[1] for those that don't know yet, the prototype is:
rw_kiovec(struct file * filp, int rw, int nr,
struct kiobuf ** kiovec, int flags,
size_t size, loff_t pos);
--
Whip me. Beat me. Make me maintain AIX.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] hashed device lookup (New Benchmarks), David S. Miller |
|---|---|
| Next by Date: | Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1, David S. Miller |
| Previous by Thread: | [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1, David S. Miller |
| Next by Thread: | Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |