From owner-freebsd-arm@FreeBSD.ORG Fri Dec 20 20:24:42 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB2B2AA0; Fri, 20 Dec 2013 20:24:42 +0000 (UTC) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1CCB61765; Fri, 20 Dec 2013 20:24:41 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id t60so2978801wes.34 for ; Fri, 20 Dec 2013 12:24:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=LBL+TalX07IhsIYju6kZkVV+BC08eK9CLenVHgV3ExM=; b=FqFQREblJT9OFVgR6RBnf3I8LAYY6zfGq3Fp0lldxLh87d4SIaAmdeMRZk7ARafZZG Ga0LULa5nDFWI+5ttPAv53dNnKTKmLTYgeLcZCBOGiMUu4gtTN78RgnNBoWOX8OrMXM9 yzuXAiZPCH9vKcNkV1xld/aDvqzrhtBOR4jf3laVEv6I2IzksetUol8m5unGMxx0Qk3p R1XEzc2pLRhKWOBDdUMXwXR64QSWcykXZWqhxdzheh39xx1fLxpRxhWqdlT1HXDlDlbw 2zypTG2f0DciGABGruRvqPmH0raZ9K1V5ahWUAqsfM8O7EfJ22ECCSzEkRz3Jk/Vi+eb BOfA== MIME-Version: 1.0 X-Received: by 10.180.106.200 with SMTP id gw8mr9107171wib.50.1387571080375; Fri, 20 Dec 2013 12:24:40 -0800 (PST) Sender: zbodek@gmail.com Received: by 10.217.112.65 with HTTP; Fri, 20 Dec 2013 12:24:40 -0800 (PST) In-Reply-To: References: <05740C4C-4B02-4567-9E46-E739ECEDA797@bsdimp.com> Date: Fri, 20 Dec 2013 21:24:40 +0100 X-Google-Sender-Auth: 0SuAfPShWJ-o-OOzaLxt1FvnZEQ Message-ID: Subject: Re: R-PI fixes for dhclient/sshd? From: Zbigniew Bodek To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Dec 2013 20:24:42 -0000 2013/12/20 Adrian Chadd : > On 20 December 2013 10:34, Zbigniew Bodek wrote: >> 2013/12/20 Adrian Chadd : >>> On 20 December 2013 09:29, Warner Losh wrote: >>>> >>>> On Dec 20, 2013, at 10:13 AM, Adrian Chadd wrote: >>>> >>>>> Hi, >>>>> >>>>> Did the fixes to the raspberry pi SoC support go into the tree? The >>>>> stuff that was affecting the allocator behaviour for things like >>>>> sshd/dhclient? >>>> >>>> I thought all armv6 builds were affected by this... >>> >>> Right. Well, I thought it had at least been diagnosed. >>> >>> >> Hello. >> >> If you are referring to bug related to jemalloc and pmap stuff then: >> - I was not able to reproduce this on my own (I mean on "not-rpi" machine) >> - The commit that was affecting this problem was found in pmap however >> there was no solution. >> - I'll try to post some pmap patches in the near future (sorry I was >> not able to do any concrete work lately). >> - This issue is on my mind but I since I can't touch this directly I >> can only try to find general improvements and post what have been >> found in Semihalf. > > Thanks for the update. > > What would be the harm in reverting the patch? > > http://svnweb.freebsd.org/base/head/sys/arm/arm/pmap-v6.c?r1=251370&r2=252694&pathrev=252694 > Hello again. I guess it should be some performance impact since we will need to write all pages marked as RW to backing storage on page-out. This is regardless of its actual dirty state (no modified emulation). But this was how it behaved earlier and nothing bad happened so it might be worth to temporary revert it and debug the problem without the negative influence on the users. After proper fix we should apply it again. It's up to you. I have no objections to that (I have few other patches that need to wait for pmap problems resolution anyway like pmap_copy() + SP). Best regards zbb