From owner-freebsd-current@FreeBSD.ORG Thu Aug 8 05:24:00 2013 Return-Path: Delivered-To: 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 ESMTP id 96EA0126 for ; Thu, 8 Aug 2013 05:24:00 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 60BCF25D7 for ; Thu, 8 Aug 2013 05:24:00 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id k5so1152397iea.32 for ; Wed, 07 Aug 2013 22:23:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=A6d5m82Sa/9n59wqACzPWp2Y7d3RMd9JFkFh0a1SBHM=; b=Ae3Cx3G+eNbjrpGW0kOTf7yJrTgOQbuCxWI9offPSd/vjEGgHfzSt1XECwCYkgRmqL tBSWxtNniW7Gc8LaZCUTZby45HiqMsuv660AyEeBx89D4DeuyxWBxNUHUXCVQ6Nl1+0v ZQeE+QlTUZU8aKqqN9fN+/R0MTZeFKuovjzfBJ3b0AiRGD2CSSux6iranr6JtiNeC6Hp RQj7Otvwac2bbDYM4quBnN45hsam9bBxbBSrz9qRcdl20YbLkZ+uRzwzAzhWcMlKTCmR 9CuF0cU9b8uCO8cUVqr/pRp8TXr3FQMC4nuvJ9xoKnoHCFJUHCy2cqJmAFkgZy70Z0Ps KSCg== X-Gm-Message-State: ALoCoQk8nK1iET8dzw6+9yVTEFCsAdtXVIjRN5mJ0f9SnLf/pCiiX4qyokRn9X2xv6stkwaUIhrJ X-Received: by 10.42.83.201 with SMTP id i9mr1296037icl.110.1375938998922; Wed, 07 Aug 2013 22:16:38 -0700 (PDT) Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id io8sm5063623igb.7.2013.08.07.22.16.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 Aug 2013 22:16:38 -0700 (PDT) Sender: Warner Losh Subject: Re: [net] protecting interfaces from races between control and data ? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Wed, 7 Aug 2013 23:16:36 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20130805082307.GA35162@onelab2.iet.unipi.it> <2034715395.855.1375714772487.JavaMail.root@daemoninthecloset.org> <51FFDD1E.1000206@FreeBSD.org> To: Adrian Chadd X-Mailer: Apple Mail (2.1085) Cc: current@freebsd.org, Bryan Venteicher , Navdeep Parhar , net@freebsd.org, Giuseppe Lettieri , Luigi Rizzo X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Thu, 08 Aug 2013 05:24:00 -0000 On Aug 5, 2013, at 11:20 AM, Adrian Chadd wrote: > .. and I bet it's not a design pattern, and this is total conjecture = on my part: >=20 > * the original drivers weren't SMP safe; > * noone really sat down and figured out how to correctly synchronise > all of this stuff; > * people did the minimum amount of work to keep the driver from > immediately crashing, but didn't really think things through at a > larger scale. >=20 > Almost every driver is this way Luigi. :-) Most of the drivers in the three don't support hardware that performs = well enough for this to be a problem. :) Any driver that's still around = from the pre-locking days can easily saturate the lines (or the = hardware) on today's (and even yesterday's hardware). All the rest have come up with different ways to cope... Warner