From owner-freebsd-current@FreeBSD.ORG Mon Dec 2 05:02:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83F38D5; Mon, 2 Dec 2013 05:02:53 +0000 (UTC) Received: from mail-qe0-x22d.google.com (mail-qe0-x22d.google.com [IPv6:2607:f8b0:400d:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0AA3310B2; Mon, 2 Dec 2013 05:02:52 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id 6so12836248qea.18 for ; Sun, 01 Dec 2013 21:02:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=5OZpeEVxX+5txyZVFMFemU3TsA/C5ipw0qvzHw7mRw0=; b=duNlyUeNGj9wLEaO6kiuT7UiTZfWp6NYk39dDrNzlQJe8LN/AyQsxKWZTd2Chwx/LZ 0hM6LUGOZ3t2ShHzstqgOwQLuPCWYeUIYLrF6wE1H6qTq6PiaMzSjxpB0n6VpfufrVML P7M7EoXNUMk2KmtBuMBzvI/oUDYOQBGJwLBV3ti0KucA6n8k5vrUB7hZ6G3/IijLWN89 4jIisZdhfjacqpPwU5YBEcX60/18kNIyETFOr6jfI0r9tT/LMxcTNBDpbofzThpAkxA9 RZ0F5LQpjmRAiy4Tv23GV5VDUIY76SWcx0e4AhFvByMwpfrlOE1LCPTICGiJO8rjhHoL vAtA== MIME-Version: 1.0 X-Received: by 10.229.122.195 with SMTP id m3mr109680144qcr.7.1385960572142; Sun, 01 Dec 2013 21:02:52 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Sun, 1 Dec 2013 21:02:52 -0800 (PST) In-Reply-To: References: <4053E074-EDC5-49AB-91A7-E50ABE36602E@freebsd.org> Date: Sun, 1 Dec 2013 21:02:52 -0800 X-Google-Sender-Auth: 1Fcg6ebyMlcDG_508SdPJ3VO2Qc Message-ID: Subject: Re: [PATCH] SO_REUSEADDR and SO_REUSEPORT behaviour From: Adrian Chadd To: Sepherosa Ziehau Content-Type: text/plain; charset=ISO-8859-1 Cc: =?ISO-8859-1?Q?Ermal_Lu=E7i?= , freebsd-net , Oleg Moskalenko , Tim Kientzle , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.16 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: Mon, 02 Dec 2013 05:02:53 -0000 Hi! Thanks for the writeup! On 1 December 2013 20:17, Sepherosa Ziehau wrote: > I also put up a brief description of SO_REUSEPORT in dfly; may be useful to > you: > http://leaf.dragonflybsd.org/~sephe/netisr_so_reuseport.txt Ok, so given this, how do you guarantee the UTHREAD stays on the given CPU? You assume it stays on the CPU that the initial listen socket was created on, right? If it's migrated to another CPU core then the listen queue still stays in the original hash group that's in a netisr on a different CPU? -adrian