From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jiri Pirko <jiri@resnulli.us>
Subject: Re: [patch net-next 3/4] mlxsw: Add interface to access registers
 and process events
Date: Fri, 24 Jul 2015 07:18:59 +0200
Message-ID: <20150724051859.GA2178@nanopsycho.orion>
References: <1437666216-3149-1-git-send-email-jiri@resnulli.us>
 <1437666216-3149-4-git-send-email-jiri@resnulli.us>
 <CAE4R7bAQ+AAEZL2pnbM5w-dFqxh_8VmUeG4Dqg7Ey-g9XpfTsw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Netdev <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>, idosch@mellanox.com,
	eladr@mellanox.com,
	"ogerlitz@mellanox.com" <ogerlitz@mellanox.com>,
	Roopa Prabhu <roopa@cumulusnetworks.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Thomas Graf <tgraf@suug.ch>,
	Alexei Starovoitov <ast@plumgrid.com>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	john fastabend <john.fastabend@gmail.com>,
	"simon.horman@netronome.com" <simon.horman@netronome.com>,
	John Linville <linville@tuxdriver.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	Shrijeet Mukherjee <shm@cumulusnetworks.com>,
	"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
	Jiri Pirko <jiri@mellanox.com>
To: Scott Feldman <sfeldma@gmail.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-wi0-f178.google.com ([209.85.212.178]:38401 "EHLO
	mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750862AbbGXFTD (ORCPT
	<rfc822;netdev@vger.kernel.org>); Fri, 24 Jul 2015 01:19:03 -0400
Received: by wibxm9 with SMTP id xm9so11954965wib.1
        for <netdev@vger.kernel.org>; Thu, 23 Jul 2015 22:19:01 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <CAE4R7bAQ+AAEZL2pnbM5w-dFqxh_8VmUeG4Dqg7Ey-g9XpfTsw@mail.gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

Fri, Jul 24, 2015 at 07:13:42AM CEST, sfeldma@gmail.com wrote:
>On Thu, Jul 23, 2015 at 8:43 AM, Jiri Pirko <jiri@resnulli.us> wrote:
>> From: Ido Schimmel <idosch@mellanox.com>
>>
>> Add the ability to construct mailbox-style register access messages
>> called EMADs with provisions to construct and parse the registers payload.
>> Implement EMAD transaction layer which is responsible for the reliable
>> transmission of EMADs.
>> Also, add an infrastructure used by the switch driver to register for
>> particular events generated by the device.
>
>What is this EMADs used for?  Is this for intra-switch or inter-switch
>communications?

It is used for passing configuration messages to/from switch device.
It is also used for events. EMADS are passed inside skb like ordinary
packets. They do not leave the switch.