From owner-freebsd-hackers@FreeBSD.ORG  Thu Apr 26 17:42:21 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1534C1065677
	for <freebsd-hackers@freebsd.org>; Thu, 26 Apr 2012 17:42:21 +0000 (UTC)
	(envelope-from wojtek@wojtek.tensor.gdynia.pl)
Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [89.206.35.99])
	by mx1.freebsd.org (Postfix) with ESMTP id 5299A8FC18
	for <freebsd-hackers@freebsd.org>; Thu, 26 Apr 2012 17:42:20 +0000 (UTC)
Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1])
	by wojtek.tensor.gdynia.pl (8.14.5/8.14.5) with ESMTP id q3QHgGTj001461;
	Thu, 26 Apr 2012 19:42:16 +0200 (CEST)
	(envelope-from wojtek@wojtek.tensor.gdynia.pl)
Received: from localhost (wojtek@localhost)
	by wojtek.tensor.gdynia.pl (8.14.5/8.14.5/Submit) with ESMTP id
	q3QHgG8a001458; Thu, 26 Apr 2012 19:42:16 +0200 (CEST)
	(envelope-from wojtek@wojtek.tensor.gdynia.pl)
Date: Thu, 26 Apr 2012 19:42:15 +0200 (CEST)
From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>
To: Garrett Cooper <yanegomi@gmail.com>
In-Reply-To: <CAGH67wSiP_ySU2v3VBzqzaU-D3pMDzZvXa43FP-CFRZboTu=Cg@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1204261940250.1457@wojtek.tensor.gdynia.pl>
References: <alpine.BSF.2.00.1204261913320.54086@wojtek.tensor.gdynia.pl>
	<CAGH67wSiP_ySU2v3VBzqzaU-D3pMDzZvXa43FP-CFRZboTu=Cg@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7
	(wojtek.tensor.gdynia.pl [127.0.0.1]);
	Thu, 26 Apr 2012 19:42:16 +0200 (CEST)
Cc: freebsd-hackers@freebsd.org
Subject: Re: best possible GJOURNAL device?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Apr 2012 17:42:21 -0000

>> http://www.vikingmodular.com/products/arxcis/ddr3/ddr3.html
> In general devices like these that I've dealt with in the past are
> presented as SATA or SAS devices, but some devices require additional
> drivers (take Ramdrives devices for instance).

this one - as described - is 100% regular DDR3 DIMM and plugged as normal 
memory.

>
>
> Depends on the BIOS, the settings set in the BIOS, etc.
>
>> FreeBSD is but it can be patched easily.
>
> I wouldn't depend on volatile memory working in a non-volatile manner
> unless it's battery backed (which companies like Ramdrive, STEC,

this is supercapacitor backed. after poweroff it have enough time to write 
all to SLC flash chip.


>> How to get DRAM controller mapping i mean what DIMM is at what address?
>
> What is located where should be opaque if the designer designed it
> properly (otherwise a driver will need to be added to interface with
> the device if the vendor is trying to be clever or is not fully
> conforming to ATA/SCSI standards).


please read attached link. it is NOT SATA/ATA/SAS/PCIe device.