linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brent D. Norris" <brent@biglinux.tccw.wku.edu>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 3com Driver and the 3XP Processor
Date: Mon, 11 Jun 2001 21:27:06 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.30.0106112125280.9164-100000@biglinux.tccw.wku.edu> (raw)

Thanks to Kip for clarifying why Linux doesn't use this feature, but now I
wonder why you beleive this?


--hahn@coffee.psychology.mcmaster.ca-- wrote:

> > hype it does DES without using the CPU, does linux take advantage of that?
>
> no, as far as I've heard.  and I wouldn't expect it to either.
> further, it's highly questionable whether the feature makes sense...

If they release the API for it why would you not expect it to use it, and
why would getting a complex computation and encryption off of the CPU to a
more specialized hardware not make sense?

Brent Norris

Executive Advisor -- WKU-Linux





             reply	other threads:[~2001-06-12  2:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12  2:27 Brent D. Norris [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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 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

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.LNX.4.30.0106112125280.9164-100000@biglinux.tccw.wku.edu \
    --to=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).