From owner-freebsd-scsi@FreeBSD.ORG  Wed Sep 10 19:43:36 2014
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 14327B45
 for <freebsd-scsi@freebsd.org>; Wed, 10 Sep 2014 19:43:36 +0000 (UTC)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com
 [209.85.212.172])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id A62F52D8
 for <freebsd-scsi@freebsd.org>; Wed, 10 Sep 2014 19:43:34 +0000 (UTC)
Received: by mail-wi0-f172.google.com with SMTP id q5so3655450wiv.5
 for <freebsd-scsi@freebsd.org>; Wed, 10 Sep 2014 12:43:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=SSgC5jXLFTPanu31eXuYI6vnowI+coqKhACl2wgj/jU=;
 b=NXhsZDzyuTs+LXWDDKftLMJ/z2IjNhmukpqZ3NTMTREt3+LfdYO3f74AF4Gae44TCF
 QCflerQygbWILu6io9uBftYQGfVtiDVx/zuux5rnFnHvQZ18sM3IdFz2VfGMTRMD3d4K
 0NmdcCGBWC0+LeQdU34Ba51eyX97RqXQveVo3v9fgGMrW6Mpjq9mFYxBS4L4/FoUYxHP
 ITjFQ61q0PxL25ELoszivS1ProPwJCClslKbsJmUcg7qs9O/n3gIqluOcT5azAjM4JdQ
 BRu/QJwnKlz4XwL6kxmOx1ketldMXx8Nc4oBWyMrXw4icL9Vr9Z1Spz4IjuxWpeAaqED
 xHmA==
X-Gm-Message-State: ALoCoQkeD63cWeD6oME2q6VsK6/QhkHiGiRzBje7CWeJMgKqHeBLFxCGlW4LIfYnOI4y8CUDNbqN
MIME-Version: 1.0
X-Received: by 10.180.186.10 with SMTP id fg10mr38593533wic.20.1410378206965; 
 Wed, 10 Sep 2014 12:43:26 -0700 (PDT)
Received: by 10.194.74.233 with HTTP; Wed, 10 Sep 2014 12:43:26 -0700 (PDT)
Date: Wed, 10 Sep 2014 12:43:26 -0700
Message-ID: <CAM0tzX0iHwmLt_QJ+ePtppUvFhqK7_rsdWm5PXQhtPQuyQGY2Q@mail.gmail.com>
Subject: equivalent of Linux dev loss timeout?
From: Chuck Tuffli <chuck@tuffli.net>
To: freebsd-scsi <freebsd-scsi@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi/>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Sep 2014 19:43:36 -0000

Linux SCSI initiator drivers have the ability to send transport events
(e.g. link up/down) to a module that handles reporting and removing
devices from the system. By setting a "dev loss timeout", users can
specify how long a device can be missing before it is removed from the
system.

As one example of how this is used, enthusiastic testers can run IO to
a device, yank out the cable between the initiator and the device for
less than dev loss timeout seconds, and then watch as the IO's resume
after the cable is reinserted.

Does anything like this exist in CAM or would it be up to each SIM to
implement this behavior?

--chuck