From: Christoph Hellwig <hch@infradead.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
John Chandy <john.chandy@uconn.edu>,
open-osd <osd-dev@open-osd.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 4/4] libosd: write/read_sg_kern API
Date: Mon, 1 Nov 2010 12:13:29 -0400 [thread overview]
Message-ID: <20101101161329.GA24836@infradead.org> (raw)
In-Reply-To: <1287490962-24013-1-git-send-email-bharrosh@panasas.com>
On Tue, Oct 19, 2010 at 02:22:42PM +0200, Boaz Harrosh wrote:
> From: John A. Chandy <john.chandy@uconn.edu>
>
> This is a trivial addition to the SG API that can receive kernel
> pointers. It is only used by the out-of-tree test module. So
> it's immediate need is questionable. For maintenance ease it might
> just get in, as it's very small.
>
> John.
> do you need this in the Kernel, or is it only for osd_ktest.ko?
It really shouldn't be in the tree at all. s/g lists are not something
that should be passed to a logical I/O layer.
next prev parent reply other threads:[~2010-11-01 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 12:18 [PATCHSET 0/4] libosd: scatter gather commands and stuff for 2.6.37 Boaz Harrosh
2010-10-19 12:20 ` [PATCH 1/4] libosd: Fix bug in attr_page handling Boaz Harrosh
2010-10-19 12:21 ` [PATCH 2/4] libosd: Free resources in reverse order of allocation Boaz Harrosh
2010-10-19 12:22 ` [PATCH 3/4] libosd: Support for scatter gather write/read commands Boaz Harrosh
2010-10-19 12:22 ` [PATCH 4/4] libosd: write/read_sg_kern API Boaz Harrosh
2010-10-19 14:13 ` Boaz Harrosh
2010-10-19 14:13 ` [PATCH 4/4 ver2] " Boaz Harrosh
2010-10-22 17:32 ` Vladislav Bolkhovitin
2010-10-24 9:55 ` Boaz Harrosh
2010-10-25 18:50 ` Vladislav Bolkhovitin
2010-10-26 10:07 ` Boaz Harrosh
2010-10-20 14:28 ` [PATCH 4/4] " John Chandy
2010-10-21 12:13 ` Boaz Harrosh
2010-11-01 16:13 ` Christoph Hellwig [this message]
2010-11-02 8:33 ` 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=20101101161329.GA24836@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@suse.de \
--cc=bharrosh@panasas.com \
--cc=john.chandy@uconn.edu \
--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).