From: Bharath Madhavan <bharath_madhavan@ivivity.com>
To: linux-kernel@vger.kernel.org
Subject: Accelerated TCP/IP support from kernel
Date: Thu, 24 May 2001 18:16:17 -0400 [thread overview]
Message-ID: <25369470B6F0D41194820002B328BDD207179D@ATLOPS> (raw)
Hello all,
I am looking into a scenario where we have a NIC which performs
all the TCP/IP processing and basically the core CPU offloads all data from
the socket level interface onwards to this NIC.
Can Linux do this as of now. I saw some limited support like TCP/IP
checksumming
being done in HW (ex: 3c905c) and linux supports it. I also saw the
ZERO_COPY
feature in linux code.
My question is can there be support for entire (almost) TCP/IP to be
offloaded
to a NIC card. I noticed some NIC cards by Alacritec and Applicom who have
such NICs but it looks like the support from Linux would be quite a bit of
work.
Basically Linux needs to support all socket calls as it will usually but
the socket interface must be intelligent enough to call different drivers(!)
for those NIC cards and thus bypassing the whole of TCP/IP stack of Linux.
Is this possible at all and if so, is anyone doing this???
I talked to a vendor who does this NIC and he said that they provide a
library
for linux which means that they have proprietery functions for using their
NIC
and thus this cannot be used in the standard socket interface way. That is a
big
limitation and not of much use. Basically, I am looking into a case where
the kernel code needs to be changed to handle this
Looking eagerly for some help/advice from you folks
Thanks a lot
Bharath
next reply other threads:[~2001-05-24 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 22:16 Bharath Madhavan [this message]
2001-05-24 22:28 ` David S. Miller
2001-05-24 22:50 Bharath Madhavan
2001-05-24 23:07 ` David S. Miller
2001-05-24 23:51 ` Gerhard Mack
2001-05-25 13:51 Bharath Madhavan
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=25369470B6F0D41194820002B328BDD207179D@ATLOPS \
--to=bharath_madhavan@ivivity.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
all inboxes | Powered by JetHome®