Minor correction:  The value of "<adapter>" in the command line, such as

    ddrdrivectl backup <adapter>

is actually the driver name and the instance number, such as 
"ddrdrive0".  This is displayed by list output.  Here's example output 
from list -v:

    % ddrdrivectl list -v
    ddrdrive0: /dev/dsk/c5d0
      model: DDRdrive X1 rev 30
      serial: 23290000000013
      capacity: 4.160 GB

(Note that the serial number is actually a SCSI-3 WWN, formed by a 
concatenation of the 24-bit OUI and the vendor supplied serial number.)

Or without -v

    % ddrdrivectl list
    ddrdrive0: /dev/dsk/c5d0


If I had multiple units, each would be listed in its own stanza.

    -- Garrett

Garrett D'Amore - sun microsystems wrote:
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
>        DDRdrive X1 driver
>     1.2. Name of Document Author/Supplier:
>        Author:  Garrett D'Amore
>     1.3  Date of This Document:
>       29 November, 2009
> 4. Technical Description
>
> This project aims to supply a new device driver, ddrdrive, to support
> the DDRdrive X1 hybrid DDR RAM and NAND solid state storage adapter
> (www.ddrdrive.com).  The only model supported is the X1, which is
> identified by PCI id pci19e3,dd52.
>
> We are seeking Patch binding for this case, although we have no specific
> plans to backport at this time.
>
> The ddrdrive driver is dependent on the new "bd" block device driver,
> specified in PSARC 2009/646.
>
> The physical device is a PCIe x1 card with 4GB of RAM and 4GB of NAND,
> with an external power supply (suitable for connection to a UPS).  It
> offers excellent write latencies, and is a good choice for a ZFS SLOG
> device.
>
>
> The device has one unusual attribute, however, which is the way data
> is moved between NAND flash and DDR RAM.  The DDR RAM remains valid
> as long as power is supplied either via the PCIe bus, or via the external
> AC power adapter.  If both power sources are lost, the DDR resets and
> any data not backed up to NAND is lost.
>
> The data is only moved between NAND and RAM on demand, and can take up
> to 60 seconds to copy (either for backup of DDR to NAND or for restoring
> NAND to to DDR.) The device only supports a complete backup or restore
> operation.
>
> In order to support this functionality, a new command, "ddrdrivectl", is
> provided by this case.  It has the following syntax:
>
> ddrdrivectl list [-v]
>         list all adapters
> ddrdrivectl backup [-f] [-q] <adapter>
>         backup adapter to flash
> ddrdrivectl restore [-f] [-q] <adapter>
>         restore adapter from flash
> ddrdrivectl help
>         show this help message
>
> The <adapter> field is a simple whole number, representing the "instance"
> of the device as found /etc/path_to_inst.  (The "list" command is offered so
> administrators won't need to grunge through that file, though.)
>
> This command additionally has some protections, which are intended to
> prevent unsafe use of the backup or restore operation.  Specifically,
> the "restore" operation includes some checks (implemented via libdiskmgt)
> to ensure that a restore is not performed while the media is currently
> mounted or otherwise in current use by the system.  In both cases, unless
> -f is specified, the user is prompted to confirm the operation.  Both
> operations effectively "suspend" the device for about 60 seconds while
> the transfer completes.
>
> (The command also has an internal "connect" and "disconnect" subcommand,
> which are intended solely to facilitate development by allowing the target
> devices to be "detached" and thereby allowing the module to be unloaded.
> These are undocumented Project Private interfaces, though.)
>
>
> Imported Interfaces
>
> bd block DDI  Consolidation Private           PSARC 2009/646
> libdiskmgmt   Consolidation Private           Used by ddrdrivectl
>
> Exported Interfaces
>
> /kernel/drv/ddrdrive  Committed               Device driver
> /usr/sbin/ddrdrivectl Uncommitted             Command (and all subcommands).
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>       6.4.1. Consolidation C-team Name:
>               ON
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
>
>   

Reply via email to