From: James Sutherland <jas88@cam.ac.uk>
To: Pavel Machek <pavel@suse.cz>
Cc: "Brent D. Norris" <brent@biglinux.tccw.wku.edu>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: Wed, 13 Jun 2001 11:30:24 +0100 (BST) [thread overview]
Message-ID: <Pine.SOL.4.33.0106131128360.13864-100000@yellow.csi.cam.ac.uk> (raw)
In-Reply-To: <20010612161237.C33@toy.ucw.cz>
On Tue, 12 Jun 2001, Pavel Machek wrote:
> Hi!
>
> > I just had one of the "3com Etherlink 10/100 PCI NIC with 3XP processor"
> > float accross my desk, I was wondering how much the linux kernel uses the
> > 3xp processor for its encryption offloading and such. According to the
> > hype it does DES without using the CPU, does linux take advantage of that?
>
> Doing DES is uninteresting these days...
>
> That feature is useless --- everything but IPsec does encryption at
> application layer where NIC can not help.
Now, if the NIC were to integrate with OpenSSL and offload some of THAT
donkey work... Just offloading DES isn't terribly useful, as Pavel says:
apart from anything else, DES is a bit elderly now - SSH using 3DES or
Blowfish etc... How dedicated is this card? Could it be used to offload
other work?
James.
next prev parent reply other threads:[~2001-06-13 10:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 0:24 3com Driver and the 3XP Processor Brent D. Norris
2001-06-12 0:29 ` Kip Macy
2001-06-12 0:43 ` Brent D. Norris
2001-06-12 1:18 ` Kip Macy
2001-06-12 16:24 ` Alan Cox
2001-06-12 16:12 ` Pavel Machek
2001-06-13 10:30 ` James Sutherland [this message]
2001-06-14 19:13 ` Brent D. Norris
2001-06-14 21:13 ` Martin Moerman
2001-06-14 21:18 ` nick
2001-06-14 21:26 ` Kip Macy
2001-06-14 21:32 ` nick
2001-06-14 21:37 ` Kip Macy
2001-06-15 2:50 ` Dr. Kelsey Hudson
2001-06-15 2:47 ` Dr. Kelsey Hudson
2001-06-15 2:51 ` nick
2001-06-15 4:01 ` [OT] " Brent D. Norris
2001-06-15 14:45 ` Alan Cox
2001-06-15 14:59 ` Venkatesh Ramamurthy
2001-06-17 16:35 ` Pavel Machek
2001-06-16 9:04 ` Martin Moerman
2001-06-14 21:37 ` David S. Miller
2001-06-14 21:40 ` nick
2001-06-14 21:40 ` Kip Macy
2001-06-14 21:41 ` David S. Miller
2001-06-15 15:12 ` Pete Wyckoff
2001-06-15 15:37 ` David S. Miller
2001-06-15 15:52 ` Pekka Pietikainen
2001-06-16 9:12 ` Martin Moerman
2001-06-18 14:43 ` Jamie Lokier
2001-06-25 15:42 ` Jes Sorensen
2001-06-14 21:45 ` David S. Miller
2001-06-14 21:48 ` Kip Macy
2001-06-14 21:51 ` David S. Miller
2001-06-25 15:45 ` Jes Sorensen
2001-06-12 16:27 ` Alan Cox
2001-06-12 2:27 Brent D. Norris
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=Pine.SOL.4.33.0106131128360.13864-100000@yellow.csi.cam.ac.uk \
--to=jas88@cam.ac.uk \
--cc=brent@biglinux.tccw.wku.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).