From: Kip Macy <kmacy@netapp.com>
To: "Brent D. Norris" <brent@biglinux.tccw.wku.edu>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: Mon, 11 Jun 2001 17:29:46 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.10.10106111729110.22254-100000@orbit-fe.eng.netapp.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0106111918550.8612-100000@biglinux.tccw.wku.edu>
It can't because 3com hasn't implemented in the driver and they won't
publish the interface.
-Kip
On Mon, 11 Jun 2001, Brent D. Norris wrote:
> 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?
>
> Brent Norris
>
> Executive Advisor -- WKU-Linux
>
> System Administrator -- WKU-Center for Biodiversity
> Best Mechanical
>
> W: 270-745-8864
> H: 270-563-9226
>
> "The problem with the Linux learning curve is that it is _so_ steep once
> at the top you can't see the people at the bottom" --Doug Hagan
>
> -
> 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/
>
next prev parent reply other threads:[~2001-06-12 0: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 [this message]
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
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.GSO.4.10.10106111729110.22254-100000@orbit-fe.eng.netapp.com \
--to=kmacy@netapp.com \
--cc=brent@biglinux.tccw.wku.edu \
--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;
as well as URLs for NNTP newsgroup(s).