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>
Cc: Jeff Garzik <jeff@garzik.org>, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH 0/] OSD changes for 2.6.31
Date: Wed, 10 Jun 2009 12:10:46 +0300 [thread overview]
Message-ID: <4A2F7896.2070905@panasas.com> (raw)
In-Reply-To: <4A197CB5.60709@panasas.com>
On 05/24/2009 07:58 PM, Boaz Harrosh wrote:
> These are the accumulated osd patches for the next merge window,
> Linux 2.6.31.
>
> Most of these patches are a repost rebased on latest scsi-misc
>
> List of patches:
> [PATCH 01/10 resend] libosd: OSD2r05: Additional command enums
> [PATCH 02/10 resend] libosd: OSD2r05: Attribute definitions
> [PATCH 03/10 resend] libosd: Better printout of OSD target system information
> [PATCH 04/10 resend] libosd: osd_req_{read,write}_kern new API
> [PATCH 05/10 resend] libosd: Let _osd_req_finalize_data_integrity receive number of out_bytes
> [PATCH 06/10 resend] libosd: osd_req_{read,write} takes a length parameter
>
> These are a resend. The last 2 patches are important for supporting Jeff's
> osdblk driver. (The first 4 are old patches that thier time has come)
>
> [PATCH 07/10] libosd: Define an osd_dev wrapper to retrieve the request_queue
> Simple wrapper
>
> [PATCH 08/10] osduld: use filp_open() when looking up an osd-device
>
> This patch was inspired by Al Viro. It uses the in-kernel open-file
> mechanism to look up the osd char-device for Kernel users like exofs
> and later pNFS-Objlayout.
> It was heavily tested and works well.
> It fixes the problem we had before, of need to open+close a file handle
> on the osd-char-device before mounting an exofs.
> Please review
>
> [PATCH 09/10] libosd: Use REQ_QUIET requests.
> Recent scsi_lib changes, caused a dmesg span in exofs+osd regular use,
> because of the way we routinely receive a recovered scsi sense. Recently, for
> reason I could not find, this condition started to print messages at:
> scsi_io_comlition:778 (look for "== RECOVERED_ERROR")
> Use of a REQ_QUIET flag is needed to silence these prints.
> OSD has it's own prints for scsi-sense returns, when needed.
>
> [PATCH 10/10] osd: Remove out-of-tree left overs
>
The merge window has risen upon us and these patches are still not
in scsi-misc. (Luckily they where in linux-next through the osd tree)
If these will not go into 2.6.31 I'm very screwed, with the pNFS stuff,
Please reconsider?
Thanks in advance
Boaz
next prev parent reply other threads:[~2009-06-10 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 16:58 [PATCH 0/] OSD changes for 2.6.31 Boaz Harrosh
2009-05-24 17:00 ` [PATCH 01/10 resend] libosd: OSD2r05: Additional command enums Boaz Harrosh
2009-05-24 17:01 ` [PATCH 02/10 resend] libosd: OSD2r05: Attribute definitions Boaz Harrosh
2009-05-24 17:01 ` [PATCH 03/10 resend] libosd: Better printout of OSD target system information Boaz Harrosh
2009-05-24 17:02 ` [PATCH 04/10 resend] libosd: osd_req_{read,write}_kern new API Boaz Harrosh
2009-05-24 17:04 ` [PATCH 05/10 resend] libosd: Let _osd_req_finalize_data_integrity receive number of out_bytes Boaz Harrosh
2009-05-24 17:04 ` [PATCH 06/10 resend] libosd: osd_req_{read,write} takes a length parameter Boaz Harrosh
2009-05-24 17:04 ` [PATCH 07/10] libosd: Define an osd_dev wrapper to retrieve the request_queue Boaz Harrosh
2009-05-24 17:05 ` [PATCH 08/10] osduld: use filp_open() when looking up an osd-device Boaz Harrosh
2009-05-24 17:05 ` [PATCH 09/10] libosd: Use REQ_QUIET requests Boaz Harrosh
2009-05-24 17:05 ` [PATCH 10/10] osd: Remove out-of-tree left overs Boaz Harrosh
2009-05-25 14:39 ` [PATCH 0/] OSD changes for 2.6.31 Jeff Garzik
2009-05-25 14:54 ` James Bottomley
2009-05-25 15:15 ` Boaz Harrosh
2009-05-25 15:44 ` Jeff Garzik
2009-06-10 9:10 ` Boaz Harrosh [this message]
2009-06-10 14:03 ` James Bottomley
2009-06-10 14:28 ` 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=4A2F7896.2070905@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 \
--cc=viro@ZenIV.linux.org.uk \
/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