linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: kmacy@netapp.com (Kip Macy)
Cc: brent@biglinux.tccw.wku.edu (Brent D. Norris),
	kmacy@netapp.com (Kip Macy),
	linux-kernel@vger.kernel.org (Linux Kernel List)
Subject: Re: 3com Driver and the 3XP Processor
Date: Tue, 12 Jun 2001 17:24:41 +0100 (BST)	[thread overview]
Message-ID: <E159qy9-0001aL-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.GSO.4.10.10106111812370.22254-100000@orbit-fe.eng.netapp.com> from "Kip Macy" at Jun 11, 2001 06:18:51 PM

> My opinion is that if you have to obscure your interface to protect your
> margins because you are making a commodity component then you are in the
> wrong business. Nonetheless they can correctly point out that they are

Cryto hardware is commodity. In fact its questionable it has any value below
1Gbit/second anyway because the cheapest low speed crypto coprocessors are
made by AMD and intel. They fit into the second socket on your dual cpu
motherboard and as well as being mass market are conveinently reprogrammable
and able to run your applications when not doing crypto. The cheapest raid
accelerator is the same story. It costs a lot of money to build custom
hardwae, an x86 is the wrong solution but its sufficiently large a hamemr
that it works better than the elegant approach for most cases.

> still making a lot more money than I am :-).

That I doubt looking at recent financial reports

But I'd be inclined to ask 3com 

   What other large company helped design the interface and owns some of the IP
   Does that other company have an interest in the OS business.

I don't know for sure but I suspect that would give a most interesting answer


  reply	other threads:[~2001-06-12 16:26 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 [this message]
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=E159qy9-0001aL-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=brent@biglinux.tccw.wku.edu \
    --cc=kmacy@netapp.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;
as well as URLs for NNTP newsgroup(s).