2003-01-08 00:47:59

by Nick

[permalink] [raw]
Subject: 3CR990 question (Nearly unrelated to iSCSI)

On Wed, 8 Jan 2003, Andrew McGregor wrote:
> > AH permits multiple digests, they also happen to correspond to the
> > hardware accelerated ones on things like the 3c990...
Speaking of which, did this driver which was mentioned ever occur?
Nick



2003-01-08 01:52:16

by Jeff Garzik

[permalink] [raw]
Subject: Re: 3CR990 question (Nearly unrelated to iSCSI)

On Tue, Jan 07, 2003 at 07:56:37PM -0500, [email protected] wrote:
> On Wed, 8 Jan 2003, Andrew McGregor wrote:
> > > AH permits multiple digests, they also happen to correspond to the
> > > hardware accelerated ones on things like the 3c990...
> Speaking of which, did this driver which was mentioned ever occur?

Two did, actually :)

I hope we will see it appear in a kernel RSN

2003-01-08 19:41:53

by Ion Badulescu

[permalink] [raw]
Subject: Re: 3CR990 question (Nearly unrelated to iSCSI)

On Tue, 7 Jan 2003 21:00:33 -0500, Jeff Garzik <[email protected]> wrote:
> On Tue, Jan 07, 2003 at 07:56:37PM -0500, [email protected] wrote:
>> On Wed, 8 Jan 2003, Andrew McGregor wrote:
>> > > AH permits multiple digests, they also happen to correspond to the
>> > > hardware accelerated ones on things like the 3c990...
>> Speaking of which, did this driver which was mentioned ever occur?
>
> Two did, actually :)

Actually, the 3Com driver I cleaned up does not have support for the
hardware crypto chip. Maybe the other driver you were referring to
supports it?

> I hope we will see it appear in a kernel RSN

Indeed. :) That damn legalese in 3Com's license...

In the meantime, I can separately distribute it to people who need it:
<http://www.badula.org/3c990/>.

The latest version (LK1.0.1) properly supports big-endian architectures,
tested on a sparc64.

Ion

--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.

2003-01-08 21:06:19

by David Dillow

[permalink] [raw]
Subject: Re: 3CR990 question (Nearly unrelated to iSCSI)

Ion Badulescu wrote:
> Actually, the 3Com driver I cleaned up does not have support for the
> hardware crypto chip. Maybe the other driver you were referring to
> supports it?

Yes, and no. It doesn't support it in the version I sent to Jeff. I do
have code that uses it, and a kludge to use it under 2.4. As for 2.5, I
hope to work to get it supported with the IPSEC code properly.

I do support the other offloading it will do -- VLAN, Checksum, and TCP
segmentation.

> > I hope we will see it appear in a kernel RSN
>
> Indeed. :) That damn legalese in 3Com's license...

And government work! I've got the paperwork in progress, should be RSN
as Jeff said. Word is no later than next Wednesday, though I'm pushing
for Friday.

I've got the firmware under a BSD style license that will work for us,
and the driver is completely GPL.

Dave Dillow
[email protected]