From owner-freebsd-arch@FreeBSD.ORG Mon Mar 11 23:14:16 2013 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CA594DAF for ; Mon, 11 Mar 2013 23:14:16 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id A70C2935 for ; Mon, 11 Mar 2013 23:14:15 +0000 (UTC) Received: from [192.168.135.7] (76-14-49-207.sf-cable.astound.net [76.14.49.207]) (authenticated bits=0) by ns1.feral.com (8.14.6/8.14.4) with ESMTP id r2BN7f2m088200 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 11 Mar 2013 16:07:41 -0700 (PDT) (envelope-from mjacob@freebsd.org) Message-ID: <513E63BC.9020105@freebsd.org> Date: Mon, 11 Mar 2013 16:07:40 -0700 From: Matthew Jacob Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-arch@freebsd.org Subject: Re: Unmapped buffers: to be merged in several days References: <20130311091852.GR3794@kib.kiev.ua> <86k3pe1cl3.fsf@ds4.des.no> <20130311182454.GX3794@kib.kiev.ua> <329178079.20130312010425@serebryakov.spb.ru> <20130311211158.GE3794@kib.kiev.ua> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Mon, 11 Mar 2013 16:07:41 -0700 (PDT) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mjacob@freebsd.org List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 23:14:16 -0000 On 3/11/2013 3:22 PM, Jim Harris wrote: > On Mon, Mar 11, 2013 at 2:11 PM, Konstantin Belousov wrote: > >> FWIW, I tried to get an Intel documentation for IOAT engine which should >> allow to perform the XOR checksumming of the unmapped buffers, suitable >> for e.g. hardware-assisted software raid5, but did not succeeded. >> > Please note that XOR checksumming support only exists in the > E5-1600/2400/2600/4600 series (Sandy Bridge Xeon) and C5500/C3500 series > (Jasper Forest - based on Nehalem Xeon) processors. The SNB Xeon series > It's been our experience at Xyratex that the h/w XOR checksum engine is generally slower than the CPU, at least with more modern Sandy Bridge chipsets. But, as you know, YMMV.