All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	open-osd mailing-list <osd-dev@open-osd.org>
Subject: [PATCHSET 0/5] osd: Revised patches for the 2.6.33 merge window
Date: Mon, 26 Oct 2009 18:51:00 +0200	[thread overview]
Message-ID: <4AE5D374.80400@panasas.com> (raw)

Hi James

I've revisited my last patches, and am submitting a new set. They address
the concern you had that I was searching for devices by /dev/* names where
actually user-mode can change those.

Additionally there is a related bugfix.

These are the patches

[PATCH 1/5] libosd: osd_dev_is_ver1 - Minor API cleanup
[PATCH 2/5] libosd: osd_sense: OSD_CFO_PERMISSIONS
	Same as before, please submit regardless.

[PATCH 3/5] osduld: Ref-counting bug fix
	This is a bug fix. In the long past it used to work, by chance.
	With this fix it does what it's suppose to do.
	(Please submit)

[PATCH 4/5] osduld: Use device->release instead of internal kref
[PATCH 5/5] libosd: osd_dev_info: Unique Identification of an OSD device
	These two patches are new implementation to the API introduced in previous
	patchset. (Plus a related addition needed by multy-device exofs support).

	It will now use the class_find_device() API to iterate through devices looking
	for the requested one. Using class_find_device forced a ref-counting shift.
	(Please review and submit)

I've tested these patches with multy-device exofs installation also exported to
pnfs-objects clients (also in multi-device) and I'm satisfied with the results.
There are no apparent new instabilities.

I would want to submit a substantial patchset to exofs, supporting multiple devices,
mirror operations. The exofs patches are dependent on these patches to osd

[I'm putting these patches and a rebased set of exofs in linux-next. There should be
 no problems merging once they get accepted into scsi-misc. As these patches are
 based on by exofs and pnfs-objects]

Thanks
Boaz

             reply	other threads:[~2009-10-26 16:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 16:51 Boaz Harrosh [this message]
2009-10-26 16:56 ` [PATCH 1/5] libosd: osd_dev_is_ver1 - Minor API cleanup Boaz Harrosh
2009-10-26 16:57 ` [PATCH 2/5] libosd: osd_sense: OSD_CFO_PERMISSIONS Boaz Harrosh
2009-10-26 16:57 ` [PATCH 3/5] osduld: Ref-counting bug fix Boaz Harrosh
2009-10-26 16:58 ` [PATCH 4/5] osduld: Use device->release instead of internal kref Boaz Harrosh
2009-10-29 17:11   ` James Bottomley
2009-10-29 17:24     ` Boaz Harrosh
2009-10-29 17:41       ` James Bottomley
2009-10-29 17:50         ` Boaz Harrosh
2009-10-29 18:03           ` James Bottomley
2009-10-29 18:10             ` Boaz Harrosh
2009-10-29 18:05           ` Boaz Harrosh
2009-10-29 17:58         ` Boaz Harrosh
2009-10-29 18:06           ` James Bottomley
2009-11-01 16:43   ` [PATCH 4/5 version 2] " Boaz Harrosh
2009-10-26 16:58 ` [PATCH 5/5] libosd: osd_dev_info: Unique Identification of an OSD device Boaz Harrosh
2009-11-01 16:45   ` [PATCH 5/5 version2] " Boaz Harrosh

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=4AE5D374.80400@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=osd-dev@open-osd.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.