From: Michael Neuling <mikey@neuling.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org,
James.Bottomley@HansenPartnership.com, nab@linux-iscsi.org,
brking@linux.vnet.ibm.com, imunsie@au1.ibm.com,
"Manoj N. Kumar" <manoj@linux.vnet.ibm.com>
Subject: Re: [PATCH RFC 1/2] cxlflash: Base support for IBM CXL Flash Adapter
Date: Wed, 27 May 2015 16:37:58 +1000 [thread overview]
Message-ID: <1432708678.15474.32.camel@neuling.org> (raw)
In-Reply-To: <20150511090941.GD28820@infradead.org>
Christoph,
> On Sun, Apr 26, 2015 at 11:50:20PM -0500, Matthew R. Ochs wrote:
> > SCSI device driver to support filesystem access on the IBM CXL Flash adapter.
>
> Please drop all the code related to your weird direct access ioctls
> from this patch. Without that it looks mostly mergeable.
What's your issue with this? Do you just not like direct access at all,
or the way it's been done?
The CAPI hardware allows devices to have direct access to userspace
memory via an MMU. What this driver is doing is enabling this direct
access so the flash controller can share memory (like queues) directly
with userspace without the kernel overhead.
Mikey
next prev parent reply other threads:[~2015-05-27 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 4:50 [PATCH RFC 1/2] cxlflash: Base support for IBM CXL Flash Adapter Matthew R. Ochs
2015-05-11 9:09 ` Christoph Hellwig
2015-05-12 4:11 ` Matthew R. Ochs
2015-05-15 20:58 ` Matthew R. Ochs
2015-05-27 6:37 ` Michael Neuling [this message]
2015-07-02 8:08 ` Seymour, Shane M
2015-07-02 15:27 ` Matthew R. Ochs
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=1432708678.15474.32.camel@neuling.org \
--to=mikey@neuling.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=brking@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=imunsie@au1.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=manoj@linux.vnet.ibm.com \
--cc=mrochs@linux.vnet.ibm.com \
--cc=nab@linux-iscsi.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.