From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 28 15:14:43 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 768474BE; Fri, 28 Jun 2013 15:14:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id 2D0A01210; Fri, 28 Jun 2013 15:14:43 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id a1so1433179qcx.11 for ; Fri, 28 Jun 2013 08:14:42 -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:cc:content-type; bh=0Ja9SSYkQ5OVS0IeF0GxlqvGQs1+THDZaHw3fQODPgU=; b=FfadSADTw10oi8lt14BLf/OAMgX5UTOrb7OdLRxUqVc733YRsuz7EFkTnXAeq5BTuz CSM62MOh4FTXShMj5EOb3UJcTSklgWF7Qim/Ee+5gYY4rIhkKdY3APvYOTjS8VcSBSlh oUKJueuUW5s2HpGSaZDSNaSzjGJe5+hrRe9g+/Gq1BhQkM7yovoKBzgRYajmKBNDFXpH zyFGBMc66q3uJFjH+4oag4mtonYIMBRxd2hDA15Yb6IPq37DlzNzWf7FjPjzvlhtw9Ex 61ip9lf/NLY3WSZ4z5j5WuPIKiFfcoE7gQZk/A3sg4QZm2tEmz+3PUG4jB+3t5c7Q/fk hJVw== MIME-Version: 1.0 X-Received: by 10.49.116.9 with SMTP id js9mr17949963qeb.73.1372432482694; Fri, 28 Jun 2013 08:14:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.214.7 with HTTP; Fri, 28 Jun 2013 08:14:42 -0700 (PDT) In-Reply-To: <51CD4FEA.7030605@FreeBSD.org> References: <51CCAE14.6040504@FreeBSD.org> <20130628065732.GL91021@kib.kiev.ua> <51CD4FEA.7030605@FreeBSD.org> Date: Fri, 28 Jun 2013 08:14:42 -0700 X-Google-Sender-Auth: w_WpsgOXBBzicMpBDLpkOZt_BPY Message-ID: Subject: Re: b_freelist TAILQ/SLIST From: Adrian Chadd To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Cc: Konstantin Belousov , hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jun 2013 15:14:43 -0000 .. i'd rather you narrow down _why_ it's performing better before committing it. Otherwise it may just creep up again after someone does another change in an unrelated part of the kernel. You're using instructions-retired; how about using l1/l2 cache loads, stores, etc? There's a lot more CPU counters available. You have a very cool problem to solve. If I could reproduce it locally I'd give you a hand. Thanks, -adrian