From: "" <simon@baydel.com>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP zero-copy
Date: Fri, 3 Aug 2001 10:23:18 +0100 [thread overview]
Message-ID: <3B6A7B96.1591.241743@localhost> (raw)
In-Reply-To: <15210.4821.318434.454971@pizda.ninka.net>
In-Reply-To: <663CE32D.1D4A9213.0F45C3B8@netscape.net>
I believe this behaviour is only possible for cards which have the
ability to dma what appears as a list of skb data fragments and
also has the ability to checksum the data. Namely the Alteon, now
3com, ACENIC and the sun hme device.
Does this kernel modification completely remove the need for a
copy/checksum of the data between user and kernel space on both
transmit and receive ?
I have written a driver for an Intel ixf1002 chip, which has some
surrounding HW, and is capable of checksumming and processing
dma in fragments. Is there any information on what changes I
would have to make to the driver to support zerocopy/checksum ?
Many Thanks
Simon.
>
> hochakhung@netscape.net writes:
> > Is there currently a stable implementation for zero copy on TCP
> > stack for linux2.4? Would anyone please point me to the patch if
> > there is any? Thanks a lot
>
> It is in the standard 2.4.x kernels these days, no patch is necessary.
>
> Later,
> David S. Miller
> davem@redhat.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
__________________________
Simon Haynes - Baydel
Phone : 44 (0) 1372 378811
Email : simon@baydel.com
__________________________
next prev parent reply other threads:[~2001-08-03 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15210.4821.318434.454971@pizda.ninka.net>
2001-08-02 18:23 ` TCP zero-copy hochakhung
2001-08-03 9:23 ` simon [this message]
2001-08-03 15:28 ` Andrew Theurer
2001-08-06 0:32 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B6A7B96.1591.241743@localhost \
--to=simon@baydel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox