From: Joel Becker <jlbec@evilplan.org>
To: Emmanuel Florac <eflorac@intellique.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
James Bottomley <James.Bottomley@suse.de>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: Why using configfs as the only interface is wrong for a storage target
Date: Mon, 7 Feb 2011 14:53:01 -0800 [thread overview]
Message-ID: <20110207225300.GD13518@noexit> (raw)
In-Reply-To: <20110207224407.GC13518@noexit>
On Mon, Feb 07, 2011 at 02:44:09PM -0800, Joel Becker wrote:
> It's great that Nick has fancy tools to fly around the target
> configfs space, but that's all fluff for people writing and debugging
I'm glad that Nick is excited about what configfs provides him
as a developer examining the system, but I think he goes overboard
extolling these virtues. This distracts from the core discussion of
configfs as a method of communicating the configuration to kernelspace.
Joel
--
Life's Little Instruction Book #207
"Swing for the fence."
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2011-02-07 22:53 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 [this message]
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
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=20110207225300.GD13518@noexit \
--to=jlbec@evilplan.org \
--cc=James.Bottomley@suse.de \
--cc=bvanassche@acm.org \
--cc=eflorac@intellique.com \
--cc=nab@linux-iscsi.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.