linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Jeff Garzik <jeff@garzik.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	open-osd mailing-list <osd-dev@open-osd.org>
Subject: [patchset 0/6] osd changes  for 2.6.31
Date: Thu, 07 May 2009 18:18:57 +0300	[thread overview]
Message-ID: <4A02FBE1.4000406@panasas.com> (raw)

Hi James

I'm sending some patches that have accumulated for the next merge window.
If they could sit in scsi-misc (and linux-next).

On top of these I will later send a couple of patches for
getting rid of the use of blk_rq_append_bio, as well as
support for chained-bios for Jeff's pending osdblk driver.
These should go in first, as the "other work" is rebased ontop
of these here.

These are the list of patches:

[PATCH 01/6] libosd: OSD2r05: Additional command enums
[PATCH 02/6] libosd: OSD2r05: Attribute definitions  
[PATCH 03/6] libosd: Better printout of OSD target system information

  These are just small stuff that have been added after the last merge window

[PATCH 04/6] libosd: osd_req_{read,write}_kern new API
  This is refactoring of common code used by a few library users

[PATCH 05/6] libosd: Let _osd_req_finalize_data_integrity receive number of out_bytes
[PATCH 06/6] libosd: osd_req_{read,write} takes a length parameter
  These patches are in preparation for supporting bio-chains. BIO-chains support is
  needed both by Jeff's osdblk stacking block device, as well as future work in exofs
  and pNFS-Objects layout-driver.

  The support is not yet finished until acceptance of a couple of patches to the block
  layer and corresponding patches to osd which I will send next.

Thank you in advance
Boaz

             reply	other threads:[~2009-05-07 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 15:18 Boaz Harrosh [this message]
2009-05-07 15:21 ` [PATCH 1/6] libosd: OSD2r05: Additional command enums Boaz Harrosh
2009-05-07 15:22 ` [PATCH 2/6] libosd: OSD2r05: Attribute definitions Boaz Harrosh
2009-05-07 15:25 ` [PATCH 3/6] libosd: Better printout of OSD target system information Boaz Harrosh
2009-05-07 15:27 ` [PATCH 4/6] libosd: osd_req_{read,write}_kern new API Boaz Harrosh
2009-05-07 15:29 ` [PATCH 5/6] libosd: Let _osd_req_finalize_data_integrity receive number of out_bytes Boaz Harrosh
2009-05-07 15:31 ` [PATCH 6/6] libosd: osd_req_{read,write} takes a length parameter 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=4A02FBE1.4000406@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jeff@garzik.org \
    --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 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).