From: Mike Christie <mchristi@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: ceph-devel@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 0/5] target/rbd: distributed lun reset support
Date: Tue, 05 May 2015 23:49:10 -0500 [thread overview]
Message-ID: <55499D46.9040008@redhat.com> (raw)
In-Reply-To: <20150505174939.GA21297@infradead.org>
On 05/05/2015 12:49 PM, Christoph Hellwig wrote:
> Can you explain why you want to hook into the lun reset code? I know
> the PR code needs to issue implicit task aborts, but I don't
> understand the need to do something with lun resets.
I thought if you exported a LU through multiple LIO nodes and its ALUA
state was active optimized/non-optimized on those nodes, then you would
have to do similar cleanup across the cluster. For example, don't we
have to fail commands on those other nodes, and then also depending on
the TAS bit value return task aborted statuses?
> As for the API: I would much prefer to have things at the block layer
> in some form than adding side band protocol for specific functionality.
>
Ok. For what you need for your NFS cluster work, will you have a
request_queue or block_device or gendisk?
next prev parent reply other threads:[~2015-05-06 4:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 9:56 [PATCH 0/5] target/rbd: distributed lun reset support mchristi
2015-05-05 9:56 ` [PATCH 1/5] rbd: rename rbd.c to rbd_main.c mchristi
2015-05-05 9:56 ` [PATCH 2/5] target: add cluster device init hooks mchristi
2015-05-05 9:56 ` [PATCH 3/5] target: lun reset cluster hook into support mchristi
2015-05-05 9:56 ` [PATCH 4/5] target: add helper to go from iblock to request queue mchristi
2015-05-05 9:56 ` [PATCH 5/5] rbd: implment lio cluster api module mchristi
2015-05-05 17:49 ` [PATCH 0/5] target/rbd: distributed lun reset support Christoph Hellwig
2015-05-06 4:49 ` Mike Christie [this message]
2015-05-06 6:48 ` Christoph Hellwig
2015-05-08 6:04 ` Mike Christie
2015-05-08 7:02 ` Nicholas A. Bellinger
2015-05-09 14:29 ` Christoph Hellwig
2015-05-06 4:56 ` Mike Christie
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=55499D46.9040008@redhat.com \
--to=mchristi@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.org \
--cc=target-devel@vger.kernel.org \
/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.