From owner-freebsd-wireless@FreeBSD.ORG Tue Sep 4 23:20:11 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03B12106564A; Tue, 4 Sep 2012 23:20:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C04EC8FC08; Tue, 4 Sep 2012 23:20:10 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so10283025pbb.13 for ; Tue, 04 Sep 2012 16:20:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=86UpdenUT2slDXhjLJUNDozokh/L4famIeDj7Z88L1E=; b=xazELmVya3nuNeVKy0AUEPUyvKnsEPYC0emt6k59AYYTM9i+K8ahJ1AQRG/8lfPJYQ 8m15bHkx+hQhQSJluwHxplvXtGN88otOPY//y0TkPmB3/+I2be36R8YGS6gXG9JmIX+x ZPlolkQPXo0JRVg4/rjUIJQdSoo+BsOg4taoF6fHOT7/CfLsTA9rTuDSdlXDVrZcykbF AC3aXN8pKUXOQUeBiQ4goQMzc3bKH87HvozbKHWfF3boYflW7+TwRqDBZlgUotPZxNwq wFhZkoCPTijE9/EMsKOOA7qmtJDdOzgLBAjwd0RX8CVFZ6j8pyh4IUyWsOQ7QmT5obI/ 3o5g== MIME-Version: 1.0 Received: by 10.68.236.102 with SMTP id ut6mr49416068pbc.113.1346800810177; Tue, 04 Sep 2012 16:20:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Tue, 4 Sep 2012 16:20:10 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Sep 2012 16:20:10 -0700 X-Google-Sender-Auth: mLVlNyCbl87EIsemNNbupCDk2lA Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org, freebsd-embedded@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: Heads up: AR7241 + PCIe and AR9287 on-board stuff works X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Sep 2012 23:20:11 -0000 On 28 August 2012 21:00, Adrian Chadd wrote: > The default (most things as modules) kernel build is still ~ 3.5mb. > That's rather large for a board with 16MB of RAM. > > Additionally, I can't load the ath device after the system has come up > single user - the driver fails to allocate descriptors/buffer entries. > I'll do some digging about it in a couple of weeks. I'd like some > pointers on how to dump the current state of memory so I can see > exactly what's going on. > > For reference, 'sysctl vm.vmtotal' shows the total free RAM is around > 1 to 1.5MB. I'm guessing some are allocated to buffers but I'd like to > see what else is actually holding onto memory.. It turns out memory fragmentation due to a huge (for embedded) userland are to blame. I'll see if I can get ray@ to help me port phkmalloc to -HEAD again and try to tweak the default allocator parameters to not pre-allocate large pools for each process. Seeing login, sh, etc have an RSS of 1MB is kind of scary. I'll do some more digging with procstat (when I fit it into the current image) and report back. There's also the problem of a 3.5MB "stripped down nothing but what's needed to boot and read the rootfs from SPI flash + FFS" kernel size problem. That seems slightly(!) too big.. Adrian