From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
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: Thu, 18 Jun 2015 23:56:24 -0700 [thread overview]
Message-ID: <20150619065624.GA3601@infradead.org> (raw)
In-Reply-To: <5583B957.20200@suse.de>
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.
What might make sense with the new list-based dev entry handling is to
merge the se_lun_acl and se_dev_entry, but it would be a fair amount of
work.
next prev parent reply other threads:[~2015-06-19 6:56 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 [this message]
2015-06-19 13:21 ` Hannes Reinecke
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=20150619065624.GA3601@infradead.org \
--to=hch@infradead.org \
--cc=Linux-scsi@vger.kernel.org \
--cc=agrover@redhat.com \
--cc=hare@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox