public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@us.ibm.com>
To: linux-scsi <linux-scsi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alexis Bruemmer <alexisb@us.ibm.com>, Mike Anderson <andmike@us.ibm.com>
Subject: [PATCH] libsas: move ATA bits into a separate module
Date: Wed, 13 Sep 2006 17:21:54 -0700	[thread overview]
Message-ID: <4508A0A2.2080605@us.ibm.com> (raw)

Hi all,

Per James Bottomley's request, I've moved all the libsas SATA support
code into a separate module, named sas_ata.  To satisfy his further
requirement that libsas not require libata (and vice versa), ata_sas
maintains fixed function pointer tables to various required functions
within libsas and libata.  Unfortunately, this means that libsas and
libata both require sas_ata, but sas_ata is smaller than libata.
Unloads of libata/libsas at inopportune moments are prevented by
increasing the refcounts on both modules whenever libsas detects a SATA
device (and decreasing it when the device goes away, of course).  If the
module is removed from the .config, then all of hooks into libsas/libata
should go away.

This is a rough-cut at separating out the ATA code; please let me know
what I can improve.  At the moment, I can load and talk to SATA disks
with the module enabled, as well as watch nothing happen if the module
is not config'd in.

The patch is a bit large, so here's where it lives:
http://sweaglesw.net/~djwong/docs/sas-ata_2.patch

Thanks for any feedback that you can provide!

--D

Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>

             reply	other threads:[~2006-09-14  0:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  0:21 Darrick J. Wong [this message]
2006-09-14 15:14 ` [PATCH] libsas: move ATA bits into a separate module Jeff Garzik
2006-09-14 22:40   ` [PATCH v3] " Darrick J. Wong
2006-09-14 22:49     ` Jeff Garzik
2006-09-18 19:00     ` Christoph Hellwig
2006-09-18 21:47       ` Jeff Garzik
2006-09-18 18:59 ` [PATCH] " 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=4508A0A2.2080605@us.ibm.com \
    --to=djwong@us.ibm.com \
    --cc=alexisb@us.ibm.com \
    --cc=andmike@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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