From owner-freebsd-net@FreeBSD.ORG  Sat Mar 19 02:33:34 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9EF1C16A4CE
	for <freebsd-net@freebsd.org>; Sat, 19 Mar 2005 02:33:34 +0000 (GMT)
Received: from hotmail.com (bay101-f6.bay101.hotmail.com [64.4.56.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 81DC843D3F
	for <freebsd-net@freebsd.org>; Sat, 19 Mar 2005 02:33:34 +0000 (GMT)
	(envelope-from youlinfeng@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 18 Mar 2005 18:33:34 -0800
Message-ID: <BAY101-F6971635DE0C1696D62471CD4B0@phx.gbl>
Received: from 64.4.56.201 by by101fd.bay101.hotmail.msn.com with HTTP;
	Sat, 19 Mar 2005 02:33:34 GMT
X-Originating-IP: [64.4.56.201]
X-Originating-Email: [youlinfeng@hotmail.com]
X-Sender: youlinfeng@hotmail.com
From: "Youlin Feng" <youlinfeng@hotmail.com>
To: freebsd-net@freebsd.org
Date: Sat, 19 Mar 2005 02:33:34 +0000
X-OriginalArrivalTime: 19 Mar 2005 02:33:34.0425 (UTC)
	FILETIME=[0C2AEC90:01C52C2C]
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Content-Filtered-By: Mailman/MimeDel 2.1.1
Subject: Lesson learned from working with slow HW crypto card
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2005 02:33:34 -0000


   Correction to my previous message:
   the crypto_proc kernel thread is not running at SWI_NET pri level,
   instead it is a regular kernel thread. The impact to the user
   processes is the same.