From owner-freebsd-questions@FreeBSD.ORG  Sun Jan 20 12:19:22 2008
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0F5C416A46B
	for <freebsd-questions@freebsd.org>;
	Sun, 20 Jan 2008 12:19:22 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 1359413C520;
	Sun, 20 Jan 2008 12:19:19 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47933C46.4010407@FreeBSD.org>
Date: Sun, 20 Jan 2008 13:19:18 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: s3raphi <seraphi.lord@gmail.com>
References: <14977783.post@talk.nabble.com>
In-Reply-To: <14977783.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
Subject: Re: FreeBSD 7.0-RC1 syncache problems under high load
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jan 2008 12:19:22 -0000

s3raphi wrote:

> This looks similar to something that has already been fixed in July. I am
> assuming that the July fix is included in RC1?
> http://www.nabble.com/FreeBSD-7-TCP-syncache-fix%3A-request-for-testers-to11515217.html#a11776616

Yes.  Please follow up on net@ and with a PR if no immediate solution is 
found.

Kris