All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Cathy Avery <cavery@redhat.com>
Cc: kys@microsoft.com, jejb@linux.vnet.ibm.com,
	martin.petersen@oracle.com, sthemmin@microsoft.com,
	haiyangz@microsoft.com, devel@linuxdriverproject.org,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: storvsc: Allow only one remove lun work item to be issued per lun
Date: Sat, 15 Apr 2017 07:06:47 -0700	[thread overview]
Message-ID: <20170415140647.GA12851@infradead.org> (raw)
In-Reply-To: <1492263790-11378-1-git-send-email-cavery@redhat.com>

Just add a singlethreaded workqueue for storvsc_handle_error and you'll
get serialization for all error handling for free.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Cathy Avery <cavery@redhat.com>
Cc: sthemmin@microsoft.com, linux-scsi@vger.kernel.org,
	martin.petersen@oracle.com, haiyangz@microsoft.com,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	jejb@linux.vnet.ibm.com
Subject: Re: [PATCH] scsi: storvsc: Allow only one remove lun work item to be issued per lun
Date: Sat, 15 Apr 2017 07:06:47 -0700	[thread overview]
Message-ID: <20170415140647.GA12851@infradead.org> (raw)
In-Reply-To: <1492263790-11378-1-git-send-email-cavery@redhat.com>

Just add a singlethreaded workqueue for storvsc_handle_error and you'll
get serialization for all error handling for free.

  reply	other threads:[~2017-04-15 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15 13:43 [PATCH] scsi: storvsc: Allow only one remove lun work item to be issued per lun Cathy Avery
2017-04-15 14:06 ` Christoph Hellwig [this message]
2017-04-15 14:06   ` Christoph Hellwig
2017-04-17 19:44   ` Cathy Avery
2017-04-17 19:44     ` Cathy Avery
2017-10-17 17:32 Cathy Avery

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=20170415140647.GA12851@infradead.org \
    --to=hch@infradead.org \
    --cc=cavery@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sthemmin@microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.