From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 939C121F21F for ; Thu, 29 Oct 2015 02:01:43 -0700 (PDT) Received: by oifu63 with SMTP id u63so23982106oif.2 for ; Thu, 29 Oct 2015 02:01:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=fOS00AM1Hd4COLUDkH6h7VTH2gbJLeSQDQuw8a3hbC0=; b=GgLz8lT0/ECnHtW0L+/Hm6S3zsYQ0pEZ++ekLWUGaUkzw55bWFq7OMlODB0hkqTK9h xEhal4zzPj4nPz48HaUPD/YKyNTDH+53CD0S9Qc6J7XwvLM5SjTjGdNbBZHREDbY7Hc8 A6tQqKa5YtD3erEZylgUWup3trX/7NmibpB6CiNu0gWgxSW4oZNroAG1OIA2Pi0XUAkU Q6Htwxx3EO6KSKkseXD6SPd/IHoEc+jDnvIgUhgktQd6kaT+UyGnnQT/J3950IKkOxA5 h8FtmZOKBv/anFaORy/p0zKFdcrHaVq9VQ0Ykjz1knTGEtVDK+rSq40XSy/PJyFtmxvF y2iA== MIME-Version: 1.0 X-Received: by 10.202.65.86 with SMTP id o83mr274670oia.75.1446109302162; Thu, 29 Oct 2015 02:01:42 -0700 (PDT) Received: by 10.202.61.133 with HTTP; Thu, 29 Oct 2015 02:01:42 -0700 (PDT) Date: Thu, 29 Oct 2015 10:01:42 +0100 Message-ID: From: Dave Taht To: cake@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [Cake] memory X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2015 09:02:05 -0000 There has been so much traffic here that I can't summarize. A) But a bit on memory limits - the memory limit enforced in cake is a sanity check sort of limit. There are *no* allocations of memory in it. It will not fail itself, due to running out of memory except at init time. So if you run out of memory elsewhere in the system, the normal set of bad things happen. cake's "sane - and, yes, could use more smarts" limits can reduce memory pressure elsewhere in the system by discarding things when it gets irrational, but packet memory tends to be fragmented and hard to recover cleanly in the first place. B) Similarly a HUGE waster of memory is small packets, which usually get a full slab of bytes (2k) to play with on the rx side. This problem got so bad in some testing that openwrt contains a clever (I would say that because I wrote it), patch that once we get to tons of packets more than we think is sane and we get close to running out of 2k slabs that we start reallocating packets to fit into much smaller slabs (like 512 bytes) and copying them into those. so, briefly, memory allocation and release patterns are more complex than the discussion I sort of saw go by a over the last few days. Dave T=C3=A4ht I just invested five years of my life to making wifi better. And, now... the FCC wants to make my work, illegal for people to install. https://www.gofundme.com/savewifi