From: "David S. Miller" <davem@redhat.com>
To: taka@valinux.co.jp
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zerocopy NFS for 2.5.33
Date: Mon, 09 Sep 2002 00:19:02 -0700 (PDT) [thread overview]
Message-ID: <20020909.001902.28439948.davem@redhat.com> (raw)
In-Reply-To: <20020909.161123.74745039.taka@valinux.co.jp>
From: Hirokazu Takahashi <taka@valinux.co.jp>
Date: Mon, 09 Sep 2002 16:11:23 +0900 (JST)
Using TSO code is commented out at this moment as TSO for UDP isn't
implemented yet. I'm waiting for it so that we would remove "#ifdef NotYet"
to send jumbo UDP frames without any fragmentation and any checksumming.
Then I hope we will get great performance.
Actually, device interface for what could be used is there, see
NETIF_F_FRAGLIST. No devices set this and IP never makes use of it
yet though :-)
Acenic and Tigon3 will be able to do this, probably e1000 has this
feature as well.
But it does not work how you imagine. One passes already fragmented
list of packets to card, and it can checksum the packet if you tell it
which descriptor is first of fragmented frame and which is last.
It does not do the fragmentation of UDP frames for you, only
checksumming of UDP portion. No card does what you mention.
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2002-09-09 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 7:11 Hirokazu Takahashi
2002-09-09 7:19 ` David S. Miller [this message]
2002-09-09 8:58 ` Hirokazu Takahashi
2002-09-09 9:04 ` David S. Miller
2002-09-10 1:58 Feldman, Scott
2002-09-10 3:13 ` Hirokazu Takahashi
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=20020909.001902.28439948.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=taka@valinux.co.jp \
/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
Powered by JetHome