From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: nicolas.prochazka@gmail.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 7e980beb for ; Wed, 14 Jun 2017 14:02:16 +0000 (UTC) Received: from mail-ot0-f173.google.com (mail-ot0-f173.google.com [74.125.82.173]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 31c737ae for ; Wed, 14 Jun 2017 14:02:16 +0000 (UTC) Received: by mail-ot0-f173.google.com with SMTP id s7so1454185otb.3 for ; Wed, 14 Jun 2017 07:17:09 -0700 (PDT) MIME-Version: 1.0 Sender: nicolas.prochazka@gmail.com In-Reply-To: References: From: nicolas prochazka Date: Wed, 14 Jun 2017 16:17:08 +0200 Message-ID: Subject: Re: multiple wireguard interface and kworker ressources To: "Jason A. Donenfeld" Content-Type: text/plain; charset="UTF-8" Cc: WireGuard mailing list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , thanks :) NIcolas 2017-06-14 16:13 GMT+02:00 Jason A. Donenfeld : > On Wed, Jun 14, 2017 at 4:05 PM, Jason A. Donenfeld wrote: >> Will keep a kworker at 100% CPU, even after that command completes? >> I'm unable to reproduce this here. Could you give me detailed >> environmental information so that I can reproduce this precisely? >> Something minimal and easily reproducable would be preferred. > > Okay, I have a working reproducer now, and I've isolated the issue to > the xt_hashlimit garbage collector, an issue outside the WireGuard > code base. I might look for a work around within WireGuard, however. > I'll keep you posted.