From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@suse.de>,
Boaz Harrosh <bharrosh@panasas.com>,
Joel Becker <jlbec@evilplan.org>
Subject: Re: Why using configfs as the only interface is wrong for a storage target
Date: Mon, 07 Feb 2011 12:01:29 -0800 [thread overview]
Message-ID: <1297108889.13752.241.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <AANLkTi=b0mcWp3ergh=GvUF2CvgXUDv3Rq1fHY=xKf9L@mail.gmail.com>
On Mon, 2011-02-07 at 12:41 +0100, Bart Van Assche wrote:
> On Fri, Feb 4, 2011 at 7:45 AM, Nicholas A. Bellinger
> <nab@linux-iscsi.org> wrote:
> > Please consider the following patch series for mainline target code.
> > It consists of predominately configfs bugfixes uncovered with recent SLUB
> > poison testing, and proper removal of legacy procfs target_core_mib.c code.
> > Note that the complete set of fabric independent statistics (SCSI MIBs) and
> > fabric dependent statistics will be included as native configfs group context
> > 'per value' attribute series during the .39 time frame.
>
<SNIP>
> As we all know, it is not possible for a
> storage target to make these directories appear / disappear
> automatically in configfs because of basic configfs design choices.
>
Of course it's possible to drive configfs struct config_group creation
from kernel space. That is a tool that was used during LIO v2.x -> v3.x
IOCTL -> CONFIGFS bringup and conversion, remember..?
However Joel as the configfs maintainer did not want this code in
mainline, and I dropped the patch from lio-core-2.6.git some time ago.
If you think this is a worth-while discussion to revist perhaps you
should re-create the logic, and address the issues that Joel had with
the original code.
--nab
prev parent reply other threads:[~2011-02-07 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:41 Why using configfs as the only interface is wrong for a storage target Bart Van Assche
2011-02-07 11:53 ` Joel Becker
2011-02-07 12:08 ` Bart Van Assche
2011-02-07 19:57 ` Nicholas A. Bellinger
2011-02-07 14:41 ` James Bottomley
2011-02-07 15:02 ` Emmanuel Florac
2011-02-07 20:09 ` Nicholas A. Bellinger
2011-02-07 21:38 ` Emmanuel Florac
2011-02-07 22:44 ` Joel Becker
2011-02-07 22:53 ` Joel Becker
2011-02-08 0:03 ` Nicholas A. Bellinger
2011-02-08 8:01 ` Emmanuel Florac
2011-02-07 15:10 ` Hannes Reinecke
2015-09-16 7:34 ` Sergiu
2011-02-07 18:45 ` Joel Becker
2011-02-07 20:01 ` Nicholas A. Bellinger [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=1297108889.13752.241.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@suse.de \
--cc=bharrosh@panasas.com \
--cc=bvanassche@acm.org \
--cc=jlbec@evilplan.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).