From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
target-devel <target-devel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <Linux-scsi@vger.kernel.org>,
Andy Grover <agrover@redhat.com>
Subject: Re: Merging se_dev_entry and se_lun?
Date: Fri, 19 Jun 2015 15:21:27 +0200 [thread overview]
Message-ID: <55841757.1090904@suse.de> (raw)
In-Reply-To: <20150619065624.GA3601@infradead.org>
On 06/19/2015 08:56 AM, Christoph Hellwig wrote:
> On Fri, Jun 19, 2015 at 08:40:23AM +0200, Hannes Reinecke wrote:
>> Having a list here implies that 'se_lun' can have _several_
>> se_dev_entry structure attached to it, which I found rather curious.
>>
>> Can you give me an example where this might be the case?
>> Or can we replace the list with a simple pointer or even merge both?
>
> Each initiator has it's own dev entry.
>
But isn't 'se_lun' per initiator, too?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-06-19 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 6:40 Merging se_dev_entry and se_lun? Hannes Reinecke
2015-06-19 6:56 ` Christoph Hellwig
2015-06-19 13:21 ` Hannes Reinecke [this message]
2015-06-19 13:58 ` Christoph Hellwig
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=55841757.1090904@suse.de \
--to=hare@suse.de \
--cc=Linux-scsi@vger.kernel.org \
--cc=agrover@redhat.com \
--cc=hch@infradead.org \
--cc=nab@linux-iscsi.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.