From: Christoph Hellwig <hch@infradead.org>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH 01/33] TCMU PR: first commit to implement TCMU PR
Date: Mon, 18 Jun 2018 11:12:17 +0000 [thread overview]
Message-ID: <20180618111217.GC6507@infradead.org> (raw)
In-Reply-To: <20180615182342.6239-1-lszhu@suse.com>
On Sun, Jun 17, 2018 at 12:40:56PM +0800, Zhu Lingshan wrote:
> Hello Mike and Christoph´╝î
> Thanks Mike's comment inspired me, if I understand this correctly, it is
> suggested to implement this whole solution in kernel, avoid
>  splitting PRG handling in both kernel and userspace, make it not that
> complex. I can try to implement this by sending OSD requests
> from kernel side, then we don't need tcmu-runner supporting is, no need to
> use netlink to exchange information with userspace, pure kernel code, seems
> much more simple. Do you think this may be better?
Yes. And SuSE actually ships such a backend (originally writen by
Mike), although it would still need some work to get into shape.
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-06-18 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 18:23 [PATCH 01/33] TCMU PR: first commit to implement TCMU PR Zhu Lingshan
2018-06-15 18:32 ` Zhu Lingshan
2018-06-16 5:22 ` Christoph Hellwig
2018-06-16 7:08 ` Zhu Lingshan
2018-06-16 11:04 ` Maged Mokhtar
2018-06-16 11:08 ` Zhu Lingshan
2018-06-16 19:20 ` Mike Christie
2018-06-16 19:25 ` Mike Christie
2018-06-17 4:40 ` Zhu Lingshan
2018-06-18 11:09 ` Christoph Hellwig
2018-06-18 11:10 ` Christoph Hellwig
2018-06-18 11:12 ` Christoph Hellwig [this message]
2018-06-18 11:31 ` Zhu Lingshan
2018-06-18 11:41 ` David Disseldorp
2018-06-19 14:29 ` Christoph Hellwig
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=20180618111217.GC6507@infradead.org \
--to=hch@infradead.org \
--cc=target-devel@vger.kernel.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.