From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudeep Dutt <sudeep.dutt@intel.com>
Cc: 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 04/13] misc: mic: SCIF Peer Bus
Date: Fri, 9 Jan 2015 15:07:26 -0800 [thread overview]
Message-ID: <20150109230726.GC3614@kroah.com> (raw)
In-Reply-To: <a6cd58c4c752a4848d078af397ecf341158c2725.1418237176.git.sudeep.dutt@intel.com>
On Wed, Dec 10, 2014 at 11:47:44AM -0800, Sudeep Dutt wrote:
> The SCIF peer bus is used to register and unregister SCIF peer devices
> internally by the SCIF driver to signify the addition and removal of
> peer nodes respectively from the SCIF network. This simplifies remote node
> handling within SCIF and will also be used to support device probe/remove
> for SCIF client drivers (e.g. netdev over SCIF)
>
> Reviewed-by: Nikhil Rao <nikhil.rao@intel.com>
> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> Signed-off-by: Sudeep Dutt <sudeep.dutt@intel.com>
> ---
> drivers/misc/mic/scif/scif_peer_bus.h | 63 +++++++++++++++++
> drivers/misc/mic/scif/scif_peer_bus.c | 124 ++++++++++++++++++++++++++++++++++
> 2 files changed, 187 insertions(+)
> create mode 100644 drivers/misc/mic/scif/scif_peer_bus.h
> create mode 100644 drivers/misc/mic/scif/scif_peer_bus.c
>
> diff --git a/drivers/misc/mic/scif/scif_peer_bus.h b/drivers/misc/mic/scif/scif_peer_bus.h
> new file mode 100644
> index 0000000..27ed508
> --- /dev/null
> +++ b/drivers/misc/mic/scif/scif_peer_bus.h
> @@ -0,0 +1,63 @@
> +/*
> + * Intel MIC Platform Software Stack (MPSS)
> + *
> + * Copyright(c) 2014 Intel Corporation.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License, version 2, as
> + * published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope that it will be useful, but
> + * WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * General Public License for more details.
> + *
> + * Intel SCIF driver.
> + */
> +#ifndef _SCIF_PEER_BUS_H_
> +#define _SCIF_PEER_BUS_H_
> +
> +#include <linux/device.h>
> +#include <linux/mic_common.h>
> +
> +/*
> + * Peer devices show up as PCIe devices for the mgmt node but not the cards.
> + * The mgmt node discovers all the cards on the PCIe bus and informs the other
> + * cards about their peers. Upon notification of a peer a node adds a peer
> + * device to the peer bus to maintain symmetry in the way devices are
> + * discovered across all nodes in the SCIF network.
> + */
> +/**
> + * scif_peer_dev - representation of a peer SCIF device
> + * @dev: underlying device
> + * @dnode - The destination node which this device will communicate with.
> + */
> +struct scif_peer_dev {
> + struct device dev;
> + u8 dnode;
> +};
> +
> +/**
> + * scif_peer_driver - operations for a scif_peer I/O driver
> + * @driver: underlying device driver (populate name and owner).
> + * @id_table: the ids serviced by this driver.
> + * @probe: the function to call when a device is found. Returns 0 or -errno.
> + * @remove: the function to call when a device is removed.
> + */
> +struct scif_peer_driver {
> + struct device_driver driver;
> + const struct scif_peer_dev_id *id_table;
> +
> + int (*probe)(struct scif_peer_dev *dev);
> + void (*remove)(struct scif_peer_dev *dev);
> +};
> +
> +int scif_peer_register_driver(struct scif_peer_driver *driver);
> +void scif_peer_unregister_driver(struct scif_peer_driver *driver);
> +struct scif_dev;
> +struct scif_peer_dev *
> +scif_peer_register_device(struct scif_dev *sdev);
Odd formatting, don't you think?
Please put your "predeclare scif_dev" on an earlier line by itself, as
this is a mess.
thanks,
greg k-h
next prev parent reply other threads:[~2015-01-09 23:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 19:47 [PATCH char-misc-next 00/13] misc: mic: SCIF driver Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 01/13] misc: mic: SCIF header file and IOCTL interface Sudeep Dutt
2015-01-09 23:04 ` Greg Kroah-Hartman
2015-01-09 23:57 ` Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 02/13] misc: mic: SCIF ring buffer infrastructure Sudeep Dutt
2015-01-09 23:05 ` Greg Kroah-Hartman
2015-01-10 0:28 ` Sudeep Dutt
2015-01-10 0:47 ` Greg Kroah-Hartman
2014-12-10 19:47 ` [PATCH char-misc-next 03/13] misc: mic: SCIF Hardware Bus Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 04/13] misc: mic: SCIF Peer Bus Sudeep Dutt
2015-01-09 23:07 ` Greg Kroah-Hartman [this message]
2015-01-09 23:58 ` Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 05/13] misc: mic: Common MIC header file changes in preparation for SCIF Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 06/13] misc: mic: SCIF module initialization Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 07/13] misc: mic: SCIF node queue pair setup management Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 08/13] misc: mic: SCIF open close bind and listen APIs Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 09/13] misc: mic: SCIF connections APIs i.e. accept and connect Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 10/13] misc: mic: SCIF messaging and node enumeration APIs Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 11/13] misc: mic: MIC host driver specific changes to enable SCIF Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 12/13] misc: mic: MIC card " Sudeep Dutt
2014-12-10 19:47 ` [PATCH char-misc-next 13/13] misc: mic: add support for loading/unloading SCIF driver 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=20150109230726.GC3614@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=corbet@lwn.net \
--cc=dave.jiang@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.rao@intel.com \
--cc=sudeep.dutt@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox