[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1375403856.61060.71.camel@blbiskey-desk1.amr.corp.intel.com>
Date: Thu, 01 Aug 2013 17:37:36 -0700
From: Sudeep Dutt <sudeep.dutt@...el.com>
To: Asias He <asias@...hat.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>,
"Yaozu (Eddie) Dong" <eddie.dong@...el.com>,
Arnd Bergmann <arnd@...db.de>,
"Michael S. Tsirkin" <mst@...hat.com>,
Harshavardhan R Kharche <harshavardhan.r.kharche@...el.com>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
Ashutosh Dixit <ashutosh.dixit@...el.com>,
Rob Landley <rob@...dley.net>,
Caz Yokoyama <Caz.Yokoyama@...el.com>,
Dasaratharaman Chandramouli
<dasaratharaman.chandramouli@...el.com>,
Sudeep Dutt <sudeep.dutt@...el.com>
Subject: Re: [PATCH 0/5] Enable Drivers for Intel MIC X100 Coprocessors.
On Thu, 2013-08-01 at 15:45 +0800, Asias He wrote:
> Hello Sudeep Dutt,
>
> On Wed, Jul 31, 2013 at 06:46:08PM -0700, Greg Kroah-Hartman wrote:
> > 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 |
> > > +-------------------------------------------------------------+
>
>
> Could you send the whole series to virtualization@...ts.linux-foundation.org next time?
>
Hello Asias,
I sent all the patches including the cover letter to the same recipients
and mailing lists so I am not sure why some patches did not show up in
the virtualization mailing list. The list of recipients @ [1] seems to
suggest that I did send it :(
Thanks,
Sudeep Dutt
[1] http://www.spinics.net/lists/kernel/msg1573037.html
>
> > 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
> > _______________________________________________
> > Virtualization mailing list
> > Virtualization@...ts.linux-foundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/virtualization
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists