linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"james.bottomley@suse.de" <james.bottomley@suse.de>,
	"Jiang, Dave" <dave.jiang@intel.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Danecki, Jacek" <jacek.danecki@intel.com>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	"Skirvin, Jeffrey D" <jeffrey.d.skirvin@intel.com>,
	"Nadolski, Edmund" <edmund.nadolski@intel.com>
Subject: Re: [RFC PATCH 00/10] isci: core
Date: Thu, 31 Mar 2011 02:32:28 -0400	[thread overview]
Message-ID: <20110331063227.GC32336@infradead.org> (raw)
In-Reply-To: <AANLkTikg4MdRriURN22ztCS7vEpXnQT79pybnCDnyQKo@mail.gmail.com>

On Wed, Mar 30, 2011 at 05:20:24PM -0700, Dan Williams wrote:
> I think we were already on this path, but now just need to formally
> acknowledge and accelerate in this direction.  Let me outline where I
> think we are and a rough outline of how to get to the removal of the
> wrapper.
> 
> 1/ Complete the removal of all OS agnostic indirections in the core.
> We have done quite a bit here to call kernel and lldd facilities
> directly, but still need to get rid of intel_{sas|sata|scsi}.h and
> duplicated utilities before this step is complete.
> 
> 2/ Make the core data structures member position independent (so we
> can start adding / removing fields at will).  That means getting rid
> of unnecessary casting (already started), the base_ structures (you
> started this) and the _{get|set}_association macros.
> 
> 3/ Unify the data structures so they have the same lifetimes.  Where
> the lldd has a member that duplicates a core member teach it to use
> the core version.  Quick example isci_phy.aif and
> scic_sds_phy.sas.identify_address_frame_buffer.
> 
> 4/ Remove the lldd/core data structure distinction.
> 
> Probably missing some sub-steps between three and four, but that is
> the general idea.

Yes, that's about the required stepts.  In general I'd try to do as much
as possible of the data structures before the procedural part, as that's
the design that really matters.

      reply	other threads:[~2011-03-31  6:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 10:54 [RFC PATCH 00/10] isci: core Dan Williams
2011-03-10 10:54 ` [RFC PATCH 01/10] isci/core: controller Dan Williams
2011-03-10 10:54 ` [RFC PATCH 02/10] isci/core: phy Dan Williams
2011-03-10 10:54 ` [RFC PATCH 03/10] isci/core: port Dan Williams
2011-03-10 10:54 ` [RFC PATCH 04/10] isci/core: remote device Dan Williams
2011-03-10 10:54 ` [RFC PATCH 05/10] isci/core: remote node context Dan Williams
2011-03-10 10:54 ` [RFC PATCH 06/10] isci/core: stp Dan Williams
2011-03-10 10:54 ` [RFC PATCH 07/10] isci/core: request (general, ssp and smp) Dan Williams
2011-03-10 10:55 ` [RFC PATCH 08/10] isci/core: unsolicited frame handling and registers Dan Williams
2011-03-10 10:55 ` [RFC PATCH 09/10] isci/core: base state machine and memory descriptors Dan Williams
2011-03-10 10:55 ` [RFC PATCH 10/10] isci/core: common definitions and utility functions Dan Williams
2011-03-30 14:37   ` Christoph Hellwig
2011-03-15 17:47 ` [RFC PATCH 00/10] isci: core Jeff Garzik
2011-03-15 17:55   ` Christoph Hellwig
2011-03-15 18:08     ` Jeff Garzik
2011-03-15 20:13       ` Dan Williams
2011-03-15 21:04         ` Jeff Garzik
2011-03-18 15:56 ` Christoph Hellwig
2011-03-19  6:19   ` Dan Williams
2011-03-27 22:32 ` Christoph Hellwig
2011-03-30  1:22   ` Dan Williams
2011-03-30  7:23     ` Christoph Hellwig
2011-03-31  0:20       ` Dan Williams
2011-03-31  6:32         ` Christoph Hellwig [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=20110331063227.GC32336@infradead.org \
    --to=hch@infradead.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=edmund.nadolski@intel.com \
    --cc=jacek.danecki@intel.com \
    --cc=james.bottomley@suse.de \
    --cc=jeffrey.d.skirvin@intel.com \
    --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).