All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: greg@enjellic.com, Christoph Hellwig <hch@infradead.org>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	target-devel <target-devel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Unifying the LIO and SCST target drivers
Date: Mon, 9 Feb 2015 14:16:45 +0100	[thread overview]
Message-ID: <54D8B33D.40509@sandisk.com> (raw)
In-Reply-To: <201502031006.t13A6KhM008961@wind.enjellic.com>

On 02/03/15 11:06, Dr. Greg Wettstein wrote:
> On Jan 19,  1:21am, Christoph Hellwig wrote:
>> On Thu, Jan 15, 2015 at 05:13:00PM +0100, Bart Van Assche wrote:
>>> My goal is to realize this proposal without adding hooks for out-of-tree
>>> code in the upstream kernel. What I had in mind is to raise the
>>> abstraction level of the API between LIO core and target drivers a
>>> little bit (e.g. by using accessor functions where necessary instead of
>>> accessing structure members directly)
> 
>> That's very much a hook, althiugh a week one.
>>
>> Either way I don't think bringing up a very much political topic
>> without even any code to discuss isn't a very valueable use of our time
>> slots.
> 
> There is code, no one is bothering to look at it or understand the
> issues involved.
> 
> It takes a six line patch to the in-kernel Qlogic target driver for
> SCST to leverage and contribute positively to the state of the
> in-kernel driver.  A six line patch, which if we were engaging in
> grounded engineering discussions, implements an interface which we
> haven't found anyone who suggests is unfounded.

Hi Greg,

Thanks for your feedback. Although I certainly value your work, please
note that what I proposed goes further than what you have done. If I
understood your e-mails correctly what you have done is to unify the API
between the QLogic initiator and target drivers for SCST and LIO. My
proposal comprises not only a unification of the initiator drivers but
also of the target drivers.

Last week I finally found the time to start working on an sample
implementation of such a unified driver. I hope that I will be able to
make that code available for review somewhere next week.

Bart.


  reply	other threads:[~2015-02-09 13:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 10:06 [Lsf-pc] [LSF/MM TOPIC] Unifying the LIO and SCST target drivers Dr. Greg Wettstein
2015-02-09 13:16 ` Bart Van Assche [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-06  0:01 Dr. Greg Wettstein
2015-02-12 13:04 Dr. Greg Wettstein
2015-01-14 10:05 Bart Van Assche
2015-01-15  9:08 ` [Lsf-pc] " Christoph Hellwig
2015-01-15 16:13   ` Bart Van Assche
2015-01-19  9:21     ` Christoph Hellwig
2015-01-19  9:36       ` Bart Van Assche
2015-02-20 10:49         ` Bart Van Assche
2015-02-21  0:00           ` Nicholas A. Bellinger
2015-02-25  8:43             ` Bart Van Assche
2015-02-27 21:58               ` Nicholas A. Bellinger
2015-02-28 11:59                 ` Bart Van Assche
2015-03-02  6:59                   ` Nicholas A. Bellinger
2015-03-04 10:23                     ` Bart Van Assche
2015-03-05 13:23                       ` Christoph Hellwig
2015-03-05 16:06                         ` Bart Van Assche
2015-03-05 18:38                           ` Andy Grover
2015-03-06  7:25                             ` Bart Van Assche
2015-03-06 19:15                               ` Andy Grover
2015-03-07  2:41                                 ` Sagi Grimberg
2015-03-07  6:25                                 ` Nicholas A. Bellinger
2015-03-09 16:51                                   ` Andy Grover
2015-03-06 23:10                               ` Nicholas A. Bellinger
2015-03-08 16:09                           ` Christoph Hellwig
2015-02-21 20:48           ` Sagi Grimberg
2015-02-22 16:29           ` Christoph Hellwig
2015-03-06 13:36           ` Bart Van Assche

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=54D8B33D.40509@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=greg@enjellic.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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.