From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: [PATCH v2 39/49] IB/hfi1: add sysfs routines Date: Wed, 17 Jun 2015 18:50:39 +0300 Message-ID: References: <20150615132434.29741.35258.stgit@phlsvslse11.ph.intel.com> <20150615132929.29741.87559.stgit@phlsvslse11.ph.intel.com> <32E1700B9017364D9B60AED9960492BC257513D9@fmsmsx120.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <32E1700B9017364D9B60AED9960492BC257513D9-RjuIdWtd+YbTXloPLtfHfbfspsVTdybXVpNB7YpNyf8@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Marciniszyn, Mike" Cc: Doug Ledford , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-rdma@vger.kernel.org On Wed, Jun 17, 2015 at 2:48 PM, Marciniszyn, Mike wrote: >> what's SC and what's SC-to-VL? aren't you using SM to do such mappings? if this >> and the below sysfs work-around/s for the maybe current lack of SM to >> configure the port? why do the upstream kernel has to carry ~hundreds of sysfs >> entries forever for such non-documented things? > This sysfs entries are used by PSM2 to form packets from user space. You didn't explain what's SC and what's SC-to-VL and why PSM2 can't talk to the SM to query that. >> >> +HFI1_SL2SC_ATTR(0); >> >> same comment on SL2SC same response as the above >> >> +HFI1_VL2MTU_ATTR(0); >> same comment on VL2MTU, why in sysfs?! > Same answer. same response as the above Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html