| Message ID | 20190407112320.32021-1-linus.luessing@c0d3.blue |
|---|---|
| Headers | show
Return-Path: <b.a.t.m.a.n-bounces@lists.open-mesh.org> X-Original-To: patchwork@open-mesh.org Delivered-To: patchwork@open-mesh.org Received: from open-mesh.org (localhost [IPv6:::1]) by open-mesh.org (Postfix) with ESMTP id 258B28267C; Sun, 7 Apr 2019 13:23:30 +0200 (CEST) Authentication-Results: open-mesh.org; dkim=fail reason="key not found in DNS" (0-bit key; unprotected) header.d=c0d3.blue header.i=@c0d3.blue header.b="fgujRqNp"; dkim-atps=neutral Received-SPF: None (mailfrom) identity=mailfrom; client-ip=138.201.29.205; helo=mail.aperture-lab.de; envelope-from=linus.luessing@c0d3.blue; receiver=<UNKNOWN> Received: from mail.aperture-lab.de (mail.aperture-lab.de [138.201.29.205]) by open-mesh.org (Postfix) with ESMTPS id D6198806A8 for <b.a.t.m.a.n@lists.open-mesh.org>; Sun, 7 Apr 2019 13:23:27 +0200 (CEST) From: =?utf-8?q?Linus_L=C3=BCssing?= <linus.luessing@c0d3.blue> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c0d3.blue; s=2018; t=1554636207; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=8VdSd5wfGWQfchYVozJr590aWQZCgJb0cRFo3ldJtTo=; b=fgujRqNpV0W2jTxKsj39ihpNaBG/yIQCKEcl/x/ePvttiKgFyAauw+E0HqTDfFsasF+sBq 3NaHZTZtxXci85E4pH77K+cYLZutqtsjGe2unDHsdVfZx6Nu0UneQ7+XOM4xK3Dg5LULAK wWP/jQSp9LLITr8kaj38grLUuk2QvaGQ7+cSorUXbusMoH/IQuDQnqoqjgf0HXYLYZD0cx L2+HUz+cb0sVd+YgirjnwR8+T+WuHZa3hgehWPMwT55OvJC5nh39CJ3t5spBekIuROdiNd tKgzvjAtWaxVJtIZJD2gU4xAsA9IAXdHEd4R2ir9a080OG6IGhrRclE8u7Ucaw== To: b.a.t.m.a.n@lists.open-mesh.org Date: Sun, 7 Apr 2019 13:23:18 +0200 Message-Id: <20190407112320.32021-1-linus.luessing@c0d3.blue> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=c0d3.blue; s=2018; t=1554636207; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=8VdSd5wfGWQfchYVozJr590aWQZCgJb0cRFo3ldJtTo=; b=MaVYB+2/1Z7QPQRAr4NDFBxMd8SEcCa4RRr+h/vcVEYxrE6T0wVGCpIBwLlVvjy6/OgrLl G6ygXEqCHOO7V8prU8Mgq8gWipBVytjdPtsMbp/uPeHfcH1kAjSaOvIVHLpzQkTJSHS88H klJuxefNyzCs/a6vsbtHK4GQcW0Bddg9NMITIX0Qp+g2m2a0gWy1Dz737lzfzi8E4AWk9b dhNI00HNM1kYcteDAYokJc4WRTzhmL61VrjgJz1B109jGx70kqgv10hEp5UgssLx3V2U7L fXIkmEfeE/8M+d5M+fqhxabX1cbjTaTEt1X0T7IrywnisdSGhCyVE/rM+171ig== ARC-Seal: i=1; s=2018; d=c0d3.blue; t=1554636207; a=rsa-sha256; cv=none; b=ip9fFYG9scPSw66mszu+Etn3n3AjYmQQiZPT0nJGO2w9rvBqXeQaVaAeEk+sT2LXQ9iyHi 2kgHW3iWvbtzoFwjAfYizj+yHmKigOJuuMlVA+I1SUBgtItAX1GANv7LSPsoH8B6vi7Iv5 DYmQl3VNeedxQ5uPS8tPR/N2Gc3JX9pA6tt1fRl7+3TznsLcDab2rVTBwjCUu2ILKiZXbi bGvxITBGXa9shNfgYbCJx+Ypv2La2QCwAoF7K0t5ZMW30hnfyof00yQtnrxU9kHNDMoWjD LdaNuRkIAHPmRAQJ/TfTCKlLI/vwZlysLEumq7/n8xvrAZ3Zuhcib4kjXDlKZQ== ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=linus.luessing@c0d3.blue smtp.mailfrom=linus.luessing@c0d3.blue Authentication-Results: ORIGINATING; auth=pass smtp.auth=linus.luessing@c0d3.blue smtp.mailfrom=linus.luessing@c0d3.blue Subject: [B.A.T.M.A.N.] [PATCH v4 0/2] batman-adv: increase DAT DHT timeout X-BeenThere: b.a.t.m.a.n@lists.open-mesh.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n.lists.open-mesh.org> List-Unsubscribe: <https://lists.open-mesh.org/mm/options/b.a.t.m.a.n>, <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=unsubscribe> List-Archive: <http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/> List-Post: <mailto:b.a.t.m.a.n@lists.open-mesh.org> List-Help: <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=help> List-Subscribe: <https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n>, <mailto:b.a.t.m.a.n-request@lists.open-mesh.org?subject=subscribe> Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking <b.a.t.m.a.n@lists.open-mesh.org> Errors-To: b.a.t.m.a.n-bounces@lists.open-mesh.org Sender: "B.A.T.M.A.N" <b.a.t.m.a.n-bounces@lists.open-mesh.org> |
Hi, This is the fourth attempt to increase the DAT DHT timeout to reduce the amount of broadcasted ARP Replies. To increase the timeout only for DAT DHT entries added via DHT-PUT but not for any other entry in the DAT cache the DAT cache and DAT DHT concepts are first split into two separate hash tables (PATCH 1/2). PATCH 2/2 then increases the timeout for DAT DHT entries from 5 to 30 minutes. The motivation for this patchset is based on the observations made here: https://www.open-mesh.org/projects/batman-adv/wiki/DAT_DHCP_Snooping Regards, Linus --- Changelog v2: formerly: "batman-adv: Increase DHCP snooped DAT entry purge timeout in DHT" (https://patchwork.open-mesh.org/patch/17364/) - removed the extended timeouts flag in the DHT-PUT messages introduced in v1 again - removed DHCP dependency Changelog v3: formerly: "batman-adv: Increase purge timeout on DAT DHT candidates" https://patchwork.open-mesh.org/patch/17728/ - fixed the potential jiffies overflow and jiffies initialization issues by replacing the last_dht_update timeout variable with a split of DAT cache and DAT DHT into two separate hash tables -> instead of maintaining two timeouts in one DAT entry two DAT entries are created and maintained in their respective DAT cache and DAT DHT hash tables Changelog v4: - rebased to: acfc9a214d01695 ("batman-adv: genetlink: make policy common to family")