Date: Mon, 08 Aug 2005 21:16:35 -0700 From: Sam Leffler <sam@errno.com> To: Andre Oppermann <andre@freebsd.org> Cc: Poul-Henning Kamp <phk@haven.freebsd.dk>, Michael Reifenberger <mike@Reifenberger.com>, freebsd-current@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org>, Mike Tancsa <mike@sentex.net> Subject: Re: Hifn driver in SMP (was Re: GELI - disk encryption GEOM class committed.) Message-ID: <42F82E23.9010307@errno.com> In-Reply-To: <42F786FC.1090805@freebsd.org> References: <42475.1123513974@phk.freebsd.dk> <42F786FC.1090805@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Andre Oppermann wrote: > Poul-Henning Kamp wrote: > >> I belive there is a bug in the HiFn chips that makes them do a soft reset >> under some set of circumstances which we have never been able to nail >> down. >> >> I have contacted HiFn about this and asked for a workaround, but >> they seem somewhat less than eager to work the case. >> >> I belive the message before last was that they hard reproduced it. >> >> The last message was from somebody going through the piles on a >> former employees table. > > > What's the deal with HiFn? IMHO Cavium are way better and much more > performant. > Not sure how you come to this conclusion about Cavium. Last time I looked at their h/w it was heavily firmware-based and the whole environment was problematic to integrate with crypto(9). OTOH it wasn't clear that integrating their stuff through the crypto subsystem would most effectively use their h/w; much better to integrate directly to ipsec and/or ssl using higher-level commands--just like hifn, broadcom, safenet, and everybody else. I also have my opinions about the quality of their code but that's another matter. Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42F82E23.9010307>