LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sudeep Dutt <sudeep.dutt@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: sudeep.dutt@intel.com, Arnd Bergmann <arnd@arndb.de>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Dave Jiang <dave.jiang@intel.com>,
	Nikhil Rao <nikhil.rao@intel.com>,
	Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: Re: [PATCH char-misc-next v3 00/13] misc: mic: SCIF driver
Date: Mon, 23 Feb 2015 16:45:11 -0800	[thread overview]
Message-ID: <1424738711.4956.2.camel@localhost> (raw)
In-Reply-To: <cover.1422317099.git.sudeep.dutt@intel.com>

On Mon, 2015-01-26 at 16:32 -0800, Sudeep Dutt wrote:
> ChangeLog:
> =========
> 
> v2 => v3:
> a) Formatting fixes for SCIF header file documentation, data type fixes
>    for SCIF IOCTL interface and added SCIF user space documentation in
>    scif_overview.txt as per feedback from Greg Kroah-Hartman
> 
> v1 => v2 @ https://lkml.org/lkml/2015/1/12/1029
> a) Use kernel-doc formatting for SCIF header file documentation, enhance
>    SCIF ring buffer documentation and formatting cleanup in patch 4 as
>    per feedback from Greg Kroah-Hartman
> b) SCIF bug fixes and cleanups since initial post
> 
> v1: Initial post @ https://lkml.org/lkml/2014/12/10/546
> 
> Description:
> ============
> 
> The Symmetric Communication Interface (SCIF (pronounced as skiff)) is a low
> level communications API across PCIe currently implemented for MIC. Currently
> SCIF provides inter-node communication within a single host platform, where a
> node is a MIC Coprocessor or Xeon based host. SCIF abstracts the details of
> communicating over the PCIe bus while providing an API that is symmetric
> across all the nodes in the PCIe network. An important design objective for SCIF
> is to deliver the maximum possible performance given the communication
> abilities of the hardware. SCIF has been used to implement an offload compiler
> runtime and OFED support for MPI implementations for MIC coprocessors.
> 

Hi Greg,

Please take a look at this patch series.

Thanks,
Sudeep Dutt


  parent reply	other threads:[~2015-02-24  0:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  0:32 Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 01/13] misc: mic: SCIF header file and IOCTL interface Sudeep Dutt
2015-03-25 11:04   ` Greg Kroah-Hartman
2015-03-26 17:53     ` Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 02/13] misc: mic: SCIF ring buffer infrastructure Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 03/13] misc: mic: SCIF Hardware Bus Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 04/13] misc: mic: SCIF Peer Bus Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 05/13] misc: mic: Common MIC header file changes in preparation for SCIF Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 06/13] misc: mic: SCIF module initialization Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 07/13] misc: mic: SCIF node queue pair setup management Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 08/13] misc: mic: SCIF open close bind and listen APIs Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 09/13] misc: mic: SCIF connections APIs i.e. accept and connect Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 10/13] misc: mic: SCIF messaging and node enumeration APIs Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 11/13] misc: mic: MIC host driver specific changes to enable SCIF Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 12/13] misc: mic: MIC card " Sudeep Dutt
2015-01-27  0:32 ` [PATCH char-misc-next v3 13/13] misc: mic: add support for loading/unloading SCIF driver Sudeep Dutt
2015-02-24  0:45 ` Sudeep Dutt [this message]
2015-03-09 16:13   ` [PATCH char-misc-next v3 00/13] misc: mic: " Sudeep Dutt
2015-03-23 16:44     ` 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=1424738711.4956.2.camel@localhost \
    --to=sudeep.dutt@intel.com \
    --cc=arnd@arndb.de \
    --cc=ashutosh.dixit@intel.com \
    --cc=corbet@lwn.net \
    --cc=dave.jiang@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikhil.rao@intel.com \
    --subject='Re: [PATCH char-misc-next v3 00/13] misc: mic: SCIF driver' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).