From owner-freebsd-current@FreeBSD.ORG Tue Aug 14 22:20:49 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7252106564A; Tue, 14 Aug 2012 22:20:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 523E28FC17; Tue, 14 Aug 2012 22:20:49 +0000 (UTC) Received: by yenl7 with SMTP id l7so1318953yen.13 for ; Tue, 14 Aug 2012 15:20:48 -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=KDVd6vUk5Ne4RLcf1CC498SJT5rsJ+p+8X0XPtvoosk=; b=If8YsXM5O5yJEnnuR2GcQ5n0s04fEmnv/x8Q9eSNZRD/H1ie6REqxeoKQyl7P0xlnc W38TRFcvTRckS7KQ9JmFbElLPsTtMqIuVVaKSnf1g2a/99Hpp9sUopehzDfzFpXF/gDf Uuv3oeasyfQD2u8mtlBmg5KKirXp3Z27GWrx8JoWlIKieoUs31I8KW7DAwXfmJQbt7E9 D7Padp7n5yBrhedG8A0l+Emu+9b694E9oc2o6qHeZ9/NlnHNheBkeW6K9f4TrXNAMXvY jS0hlyPXc1D4QgddikHCZz5TSMhTqz2bpbCz8tEcCpVW7u8PUFp/tTDarp0BQrylq3UC 2j9g== MIME-Version: 1.0 Received: by 10.66.72.197 with SMTP id f5mr22560561pav.20.1344982848112; Tue, 14 Aug 2012 15:20:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Tue, 14 Aug 2012 15:20:48 -0700 (PDT) In-Reply-To: <157941699.20120815004542@serebryakov.spb.ru> References: <157941699.20120815004542@serebryakov.spb.ru> Date: Tue, 14 Aug 2012 15:20:48 -0700 X-Google-Sender-Auth: AvFhCSoCulqcc9qsYFx0yfxA6w4 Message-ID: From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: current@freebsd.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2012 22:20:49 -0000 Hi, Would you be willing to compile a kernel with KTR so you can capture some KTR scheduler dumps? That way the scheduler peeps can feed this into schedgraph.py (and you can too!) to figure out what's going on. Maybe things aren't being scheduled correctly and the added latency is killing performance? Adrian