From owner-freebsd-mips@FreeBSD.ORG Tue Oct 4 15:48:46 2011 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A7AD106566B; Tue, 4 Oct 2011 15:48:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id F1BB28FC15; Tue, 4 Oct 2011 15:48:45 +0000 (UTC) Received: by gyf2 with SMTP id 2so790083gyf.13 for ; Tue, 04 Oct 2011 08:48:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=s0/6wASvS8gm2g9BXQNPb07JSLUTw9ibzwHWbZyRJYc=; b=TT0BnNSaE9/Nh0P3s46wEbGABiOQwiPDEV6X7xEyFpY7W6QXFN9f6crrzKGY5EQlbx Qlu764E2iwQsrQ7Ly8NU+kdRT23uT5RxH0gOLFYOy2uvs99or+mFT+faIoYgW+DEjHb1 WC/SBZBIADC79xdKX/d2mIgq+trwHUQppdnyw= MIME-Version: 1.0 Received: by 10.236.129.242 with SMTP id h78mr7445550yhi.89.1317743325488; Tue, 04 Oct 2011 08:48:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.111.42 with HTTP; Tue, 4 Oct 2011 08:48:45 -0700 (PDT) In-Reply-To: References: <20111002110331.GF1511@deviant.kiev.zoral.com.ua> Date: Tue, 4 Oct 2011 23:48:45 +0800 X-Google-Sender-Auth: AT4_vWKYz_ehevtqI783F1JvBJo Message-ID: From: Adrian Chadd To: "Jayachandran C." Content-Type: text/plain; charset=ISO-8859-1 Cc: Kostik Belousov , Alexander Motin , freebsd-mips@freebsd.org Subject: Re: svn commit: r225892 - head/sys/mips/mips X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2011 15:48:46 -0000 Hi all, I've tried jc's patch. The hand-wavy, brief summary when tested on my hostap (mips): * when doing single-stream, one way TCP tests (where it thus needs TX/RX traffic to occur), I get 100% CPU utilisation - 50% interrupt, 50% system, but the total interrupt rate isn't too high. It's much higher than without his patch. I'll go digging later to see what's going on. * when doing single-stream, one way UDP (ie, only RX traffic, no TX besides beacons and occasional other stuff), the system utilisation is better (70% system, ~ 2% interrupt). But I still see interrupt latency issues. I don't know whether it's because interrupts are missed or they're not missed but the scheduling doesn't occur until after wait has returned. I'll have to do some further digging. adrian