Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760583Ab3ICSjT (ORCPT ); Tue, 3 Sep 2013 14:39:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58711 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760409Ab3ICSjR (ORCPT ); Tue, 3 Sep 2013 14:39:17 -0400 Message-ID: <52262C8F.30107@redhat.com> Date: Tue, 03 Sep 2013 13:38:07 -0500 From: David Milburn User-Agent: Thunderbird 1.5.0.12 (X11/20081113) MIME-Version: 1.0 To: Jens Axboe CC: Asai Thambi S P , "linux-kernel@vger.kernel.org" , Sam Bradshaw Subject: Re: [PATCH] mtip32xx: Add SRSI support References: <518BE87F.3080201@micron.com> In-Reply-To: <518BE87F.3080201@micron.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1295 Lines: 36 Asai Thambi S P wrote: > This patch add support for SRSI(Surprise Removal Surprise Insertion). > > Approach: > --------- > Surprise Removal: > ----------------- > On surprise removal of the device, gendisk, request queue, device index, sysfs > entries, etc are retained as long as device is in use - mounted filesystem, > device opened by an application, etc. The service thread breaks out of the main > while loop, waits for pci remove to exit, and then waits for device to become > free. When there no holders of the device, service thread cleans up the block > and device related stuff and returns. > > Surprise Insertion: > ------------------- > No change, this scenario follows the normal pci probe() function flow. > > Signed-off-by: Asai Thambi S P > --- > drivers/block/mtip32xx/mtip32xx.c | 453 ++++++++++++++++++++++--------------- > drivers/block/mtip32xx/mtip32xx.h | 18 +- > 2 files changed, 289 insertions(+), 182 deletions(-) > Hi Jens, Will you be considering this patch for 3.12? Thanks, David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/