From owner-freebsd-stable@FreeBSD.ORG Mon Sep 18 18:19:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A8EC16A4D8 for ; Mon, 18 Sep 2006 18:19:44 +0000 (UTC) (envelope-from emosto@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.FreeBSD.org (Postfix) with ESMTP id C16BC43DA7 for ; Mon, 18 Sep 2006 18:19:36 +0000 (GMT) (envelope-from emosto@web.de) Received: from smtp05.web.de (fmsmtp05.dlan.cinetic.de [172.20.4.166]) by fmmailgate01.web.de (Postfix) with ESMTP id 48BCB1FBDCF6; Mon, 18 Sep 2006 20:19:10 +0200 (CEST) Received: from [84.153.85.23] (helo=[192.168.2.100]) by smtp05.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.107 #114) id 1GPNi1-0008AI-00; Mon, 18 Sep 2006 20:19:09 +0200 Message-ID: <450EE2A4.4030004@web.de> Date: Mon, 18 Sep 2006 20:17:08 +0200 From: Emil Stoyanov User-Agent: Thunderbird 1.5.0.5 (X11/20060809) MIME-Version: 1.0 To: Radu Adrian Zdrinca , freebsd-stable@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: emosto@web.de X-Sender: emosto@web.de Cc: Subject: Re: ath0 weak connectivity X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Sep 2006 18:19:44 -0000 Radu Adrian Zdrinca wrote: > I have had similar problems with the driver. The signal quality in > Windows is higher. But there are other problems. For example, when I > start Limewire I have to wait for about 3 minutes before it loads. I > am sure this is a problem with ath interface. > If I recall correctly, Limewire is java-based p2p app and java on Linux and FreeBSD requires a bit more resources than on Windows (according to SUN's recommendations i read the last time). I guess this is due to different strategies for memory management in the implementation of Java VM. It depends on what machines you are running java - on slower ones, or such with less memory, the time for loading java vm, and the time for allocation of memory for bigger apps may vary quite a lot, but 3 minutes looks like more problem of slow dns resolving, if many peers are connecting to you, etc.. I suppose this is not related to problems with driver, but anything is possible, just better testing and more investigations can prove that.. Cheers, Emil