From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Rusty Russell <rusty@rustcorp.com.au>,
"Michael S. Tsirkin" <mst@redhat.com>,
Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-doc@vger.kernel.org, Nikhil Rao <nikhil.rao@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>,
Caz Yokoyama <Caz.Yokoyama@intel.com>,
Dasaratharaman Chandramouli
<dasaratharaman.chandramouli@intel.com>,
Harshavardhan R Kharche <harshavardhan.r.kharche@intel.com>,
"Yaozu (Eddie) Dong" <eddie.dong@intel.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
Subject: Re: [PATCH 0/5] Enable Drivers for Intel MIC X100 Coprocessors.
Date: Wed, 31 Jul 2013 18:46:08 -0700 [thread overview]
Message-ID: <20130801014608.GD6941@kroah.com> (raw)
In-Reply-To: <cover.1374717252.git.sudeep.dutt@intel.com>
On Wed, Jul 24, 2013 at 08:31:31PM -0700, Sudeep Dutt wrote:
> An Intel MIC X100 device is a PCIe form factor add-in coprocessor
> card based on the Intel Many Integrated Core (MIC) architecture
> that runs a Linux OS. It is a PCIe endpoint in a platform and therefore
> implements the three required standard address spaces i.e. configuration,
> memory and I/O. The host OS loads a device driver as is typical for
> PCIe devices. The card itself runs a bootstrap after reset that
> transfers control to the card OS downloaded from the host driver.
> The card OS as shipped by Intel is a Linux kernel with modifications
> for the X100 devices.
>
> Since it is a PCIe card, it does not have the ability to host hardware
> devices for networking, storage and console. We provide these devices
> on X100 coprocessors thus enabling a self-bootable equivalent environment
> for applications. A key benefit of our solution is that it leverages
> the standard virtio framework for network, disk and console devices,
> though in our case the virtio framework is used across a PCIe bus.
>
> Here is a block diagram of the various components described above. The
> virtio backends are situated on the host rather than the card given better
> single threaded performance for the host compared to MIC and the ability of
> the host to initiate DMA's to/from the card using the MIC DMA engine.
>
> |
> +----------+ | +----------+
> | Card OS | | | Host OS |
> +----------+ | +----------+
> |
> +-------+ +--------+ +------+ | +---------+ +--------+ +--------+
> | Virtio| |Virtio | |Virtio| | |Virtio | |Virtio | |Virtio |
> | Net | |Console | |Block | | |Net | |Console | |Block |
> | Driver| |Driver | |Driver| | |backend | |backend | |backend |
> +-------+ +--------+ +------+ | +---------+ +--------+ +--------+
> | | | | | | |
> | | | |Ring 3| | |
> | | | |------|------------|---------|-------
> +-------------------+ |Ring 0+--------------------------+
> | | | Virtio over PCIe IOCTLs |
> | | +--------------------------+
> +--------------+ | |
> |Intel MIC | | +---------------+
> |Card Driver | | |Intel MIC |
> +--------------+ | |Host Driver |
> | | +---------------+
> | | |
> +-------------------------------------------------------------+
> | |
> | PCIe Bus |
> +-------------------------------------------------------------+
That's some nice information, why isn't it in one of the patches you
sent, so that others can read it later on to try to figure out what is
going on with this codebase?
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-01 7:30 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 3:31 [PATCH 0/5] Enable Drivers for Intel MIC X100 Coprocessors Sudeep Dutt
2013-07-25 3:31 ` [PATCH 1/5] Intel MIC Host Driver for X100 family Sudeep Dutt
2013-08-01 1:44 ` Greg Kroah-Hartman
2013-08-01 1:44 ` Greg Kroah-Hartman
2013-08-01 1:45 ` Greg Kroah-Hartman
2013-08-01 1:45 ` Greg Kroah-Hartman
2013-08-02 0:38 ` Sudeep Dutt
2013-08-02 0:38 ` Sudeep Dutt
2013-08-01 1:51 ` Greg Kroah-Hartman
2013-08-01 1:51 ` Greg Kroah-Hartman
2013-08-02 0:36 ` Sudeep Dutt
2013-08-02 0:36 ` Sudeep Dutt
2013-08-02 0:46 ` Greg Kroah-Hartman
2013-08-02 0:46 ` Greg Kroah-Hartman
2013-07-25 3:31 ` Sudeep Dutt
2013-07-25 3:31 ` [PATCH 2/5] Intel MIC Card " Sudeep Dutt
2013-07-25 3:31 ` Sudeep Dutt
2013-07-25 3:31 ` [PATCH 3/5] Intel MIC Host Driver Changes for Virtio Devices Sudeep Dutt
2013-07-25 3:31 ` Sudeep Dutt
2013-07-29 7:05 ` Michael S. Tsirkin
2013-07-29 7:05 ` Michael S. Tsirkin
2013-08-02 0:40 ` Sudeep Dutt
2013-08-02 0:40 ` Sudeep Dutt
2013-08-06 3:47 ` Rusty Russell
2013-08-06 3:47 ` Rusty Russell
2013-07-25 3:31 ` [PATCH 4/5] Intel MIC Card " Sudeep Dutt
2013-07-25 4:41 ` Greg Kroah-Hartman
2013-07-25 4:41 ` Greg Kroah-Hartman
2013-07-25 18:00 ` Sudeep Dutt
2013-07-25 18:00 ` Sudeep Dutt
2013-07-29 1:58 ` Rusty Russell
2013-07-29 1:58 ` Rusty Russell
2013-07-25 3:31 ` Sudeep Dutt
2013-07-25 3:31 ` [PATCH 5/5] Sample Implementation of Intel MIC User Space Daemon Sudeep Dutt
2013-07-25 3:31 ` Sudeep Dutt
2013-08-01 1:46 ` [PATCH 0/5] Enable Drivers for Intel MIC X100 Coprocessors Greg Kroah-Hartman
2013-08-01 1:46 ` Greg Kroah-Hartman [this message]
2013-08-01 7:45 ` Asias He
2013-08-01 7:45 ` Asias He
2013-08-02 0:37 ` Sudeep Dutt
2013-08-02 0:37 ` Sudeep Dutt
2013-08-02 0:34 ` Sudeep Dutt
2013-08-02 0:34 ` Sudeep Dutt
2013-08-13 12:43 ` Pavel Machek
2013-08-13 12:43 ` Pavel Machek
2013-08-14 20:24 ` Sudeep Dutt
2013-08-14 20:24 ` Sudeep Dutt
2013-08-15 10:14 ` Pavel Machek
2013-08-16 16:59 ` Sudeep Dutt
2013-08-16 17:08 ` Waskiewicz Jr, Peter P
2013-08-16 17:08 ` Waskiewicz Jr, Peter P
2013-08-16 16:59 ` Sudeep Dutt
2013-08-15 10:14 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2013-07-25 3:31 Sudeep Dutt
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=20130801014608.GD6941@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Caz.Yokoyama@intel.com \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=dasaratharaman.chandramouli@intel.com \
--cc=eddie.dong@intel.com \
--cc=harshavardhan.r.kharche@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nikhil.rao@intel.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=rob@landley.net \
--cc=rusty@rustcorp.com.au \
--cc=sudeep.dutt@intel.com \
--cc=virtualization@lists.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.