From owner-svn-src-all@FreeBSD.ORG Tue Feb 24 23:13:30 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7E18E167 for ; Tue, 24 Feb 2015 23:13:30 +0000 (UTC) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::11]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A149A55 for ; Tue, 24 Feb 2015 23:13:29 +0000 (UTC) X-RZG-AUTH: :JiIXek6mfvEEUpFQdo7Fj1/zg48CFjWjQv0cW+St/nW/afgnrylsiW+zbjV+ogwJ X-RZG-CLASS-ID: mo00 Received: from britannica.bec.de (ip-109-45-151-245.web.vodafone.de [109.45.151.245]) by smtp.strato.de (RZmta 37.3 DYNA|AUTH) with ESMTPSA id N056fer1OND1K2p (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) for ; Wed, 25 Feb 2015 00:13:01 +0100 (CET) Received: by britannica.bec.de (sSMTP sendmail emulation); Wed, 25 Feb 2015 00:13:00 +0100 Date: Wed, 25 Feb 2015 00:13:00 +0100 From: Joerg Sonnenberger To: svn-src-all@freebsd.org Subject: Re: svn commit: r279236 - head/sys/netinet Message-ID: <20150224231300.GA6630@britannica.bec.de> References: <201502241257.t1OCv40V097418@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201502241257.t1OCv40V097418@svn.freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2015 23:13:30 -0000 On Tue, Feb 24, 2015 at 12:57:04PM +0000, Zbigniew Bodek wrote: > In fact, the assumption that 'struct ip' is always 4-byte aligned > is definitely false, as we have no impact on data alignment of packet > stream received. Pretty much all drivers do guarantee this by setting up buffers accordingly. Why can't yours do the same? Joerg