From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Mike Christie <michaelc@cs.wisc.edu>,
Andy Grover <agrover@redhat.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] iscsi-target: Merge for .40-rc1
Date: Tue, 31 May 2011 12:19:47 +0200 [thread overview]
Message-ID: <20110531101947.GA31648@lst.de> (raw)
In-Reply-To: <BANLkTikdJcNPv4CV4nLuyuPtAYpCR1cp0Q@mail.gmail.com>
On Mon, May 30, 2011 at 05:13:22PM +0200, Bart Van Assche wrote:
> On Mon, May 30, 2011 at 3:09 PM, Christoph Hellwig <hch@lst.de> wrote:
> > Given that we pretty well tested and working code that's used in lots
> > of production setups my vote is for taking it as-is unless someone can
> > actually show a prototype for a nicely working user/kernel split.
>
> As far as I know such a user/kernel split has been implemented in both
> IET and SCST and is working fine in both of these projects.
Which are unrelated codebases - if you want to offer a competing iSCSI
implementation for the core target framework we have in mainline based
on the codebase go ahead.
> And here is another issue that still hasn't been resolved yet:
> http://marc.info/?l=linux-scsi&m=129707890023739&w=2.
This is related to the software iSCSI fronted in what way?
next prev parent reply other threads:[~2011-05-31 10:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 2:59 [GIT PULL] iscsi-target: Merge for .40-rc1 Nicholas A. Bellinger
2011-05-29 18:49 ` Linus Torvalds
2011-05-29 20:58 ` Nicholas A. Bellinger
2011-05-30 13:09 ` Christoph Hellwig
2011-05-30 15:13 ` Bart Van Assche
2011-05-31 10:19 ` Christoph Hellwig [this message]
2011-05-31 10:30 ` Bart Van Assche
2011-06-18 16:55 ` FUJITA Tomonori
2011-06-24 16:36 ` James Bottomley
2011-07-25 23:15 ` Nicholas A. Bellinger
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=20110531101947.GA31648@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=agrover@redhat.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=torvalds@linux-foundation.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.