public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: David Milburn <dmilburn@redhat.com>
Cc: Asai Thambi S P <asamymuthupa@micron.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sam Bradshaw <sbradshaw@micron.com>
Subject: Re: [PATCH] mtip32xx: Add SRSI support
Date: Tue, 03 Sep 2013 12:38:28 -0600	[thread overview]
Message-ID: <52262CA4.2030902@kernel.dk> (raw)
In-Reply-To: <52262C8F.30107@redhat.com>

On 09/03/2013 12:38 PM, David Milburn wrote:
> 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 <asamymuthupa@micron.com>
>> ---
>>  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?

Yep, it will go in this merge window.

-- 
Jens Axboe


      reply	other threads:[~2013-09-03 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 18:18 [PATCH] mtip32xx: Add SRSI support Asai Thambi S P
2013-05-10 19:21 ` Asai Thambi S P
2013-05-15  8:15   ` Jens Axboe
2013-09-03 18:38 ` David Milburn
2013-09-03 18:38   ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52262CA4.2030902@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asamymuthupa@micron.com \
    --cc=dmilburn@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sbradshaw@micron.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox