Lines Matching refs:which
42 \input{structure} % Insert the commands.tex file which contains the majority of the structure behin…
179 By definition, a driver is the entity which allows an OS to drive a hardware device.
181 …-dedicated memory (ILT), and minimal on-chip management presents a device which requires a driver …
211 …which is used by other drivers. Thus, separate drivers, including separate instances of the same d…
217 …needs and use cases of any specific OS or tool, but only with the common ground which is the ecore.
225 …\item Register-access [\ref{cha:reg}], mainly for learning about PTTs which are required by variou…
239 In addition, each chapter which includes ecore API functions that can be called by the upper-layer …
251 Most of the ecore consists of the \textit{inner} parts, i.e., HW-oriented implementation to which t…
252 Above that is a concise API layer, through which the upper-layer driver should manipulate the ecore…
286 \item \texttt{ecore\_utils.h} -- Useful macros which can be used by upper-layer driver.
305 …\item \texttt{ecore\_dbg\_fw\_funcs.[ch], ecore\_dbg\_values.h, ecore\_fw\_defs} -- Files which co…
336 …required by the ecore to perform and supply an upper level of abstraction which best suits that OS…
342 …ver consisting of the Ecore and an upper-layer, and define an API through which the various protoc…
344 The ecore utilizes various functions which should be implemented by the upper layer. There are two …
346 …emory for various reasons, and it needs the upper layer to supply the method by which it can do so.
347 …\item Hooks by which the upper-layer can run additional OS specific code, or make decisions affect…
356 …which prints will actually reach the logs based on the message urgency, defining 4 levels – verbos…
357 The \texttt{DP\_MODULE} is relevant only when level is set to verbose, and it defines which of the …
358 In order to set which prints should reach system logs, the upper layer should utilize the ecore fun…
367 …y default, this is `off'. There are several structures and field in ecore which aren't functional;…
381 …is the BAR accessed by the ecore. It is divided into configurable windows which point to different…
410 …ows, and translates the inner address into an external address [i.e., one which resides on the act…
424 …generated code known as the init-tool. Since there are quite a few values which depend upon actual…
459 …{ecore\_get\_init\_mode()} – this creates a bitmask which will be later passed to the init-tool wh…
463 … loaded on an already initialized port [FUNCTION]\footnote{Initialization which is common for both…
478 The difference is that Zipped firmware files has lot of dmae firmware data zipped which is benefici…
488 can be used by ecore clients to utilize firmware data. By default, ecore uses the .h files which ar…
508 … HW should have already been reversed by the upper-layer [e.g., L2 VPORTs which were started by th…
537 …res are allocated on host memory. The status block is an array of indices which are updated by fir…
550 There is a dedicated status block for ecore usage which is allocated and maintained by ecore.
553 The ecore defines a structure called \texttt{ecore\_sb\_info} which should be allocated by the prot…
589 …which status block generated an interrupt needs to be read from a register in the IGU. Use \myfunc…
596 In case of INTA / MSI, each function has a register in the IGU stating which status block gave the …
618 …\item (Possible upper-half handling and bottom-half scheduling, or other OS-specifics which are ou…
624 …n L2 the ecore callbacks configuring the queues will return the addresses which upper-layer should…
645 …exttt{.h} files generated by the MFW owners, e.g., \texttt{mcp\_public.h} which contains the SHMEM…
648 …lizes the Driver access to SHMEM which is used later during initialization to learn about the chip…
661 …extit{mcp\_info} struct contains as one of its fields \textit{func\_info} which is filled by the e…
665 …\item Sending messages from driver to MFW -- Each HW-function has an address in the SHMEM in which…
666 …A message is a u32 consisting of a command bit-mask which indicates of the message the HW-function…
667 In addition there’s another u32 field which might contain additional parameters [command-specific].
671 …\item Messages from MFW to driver -- MFW will trigger a general HW attention which will be handled…
672 …Per-HW-function there’s an array of message producers in SHMEM, of which the ecore maintains a co…
683 A ‘special’ instance of this function is \texttt{ecore\_mcp\_load\_req()} [which isn’t an API funct…
693 …from the MFW, it’s possible that this will eventually will call some OSAL which will need to be im…
710 …, upper driver needs to implement an OSAL [\texttt{osal\_link\_update()}] which will be called whe…
719 …which are captured under IEEE 802.3az standard. MFW negotiates the EEE parameters with the peer de…
725 Following are the EEE link parameters which can be queried by upper layer driver using \myfunc{mcp\…
764 … ecore-client. Ecore-client shouldn’t presume to do ‘push’ only for calls which match the configur…
817 This section describes in a very highlevel manner several FW objects which are related to L2. Devel…
838 …START will be sent]. The handle for this function is a \texttt{vport\_id} which is passed and the …
846 …The function is expected to receive a pointer to a \texttt{p\_ret\_params} which it will fill with…
857 …In addition, it will provide a \texttt{p\_doorbell} address, which is an address into which a door…
876 …\item Configuration of the \myindex{Rx mode} -- This defines which datagrams [unicast, multicast, …
877 …st filters -- defining filters for specific unicast / multicast addresses which should be matched,…
878 …If at least one vlan [or vlan-mac] filter will be configured only traffic which matches one of the…
881 There are several ecore functions which are responsible for configuring classifications:
983 …We can either only open $X/2$ queues on each engine, in which case we lose some abilities, e.g., c…
1011 …BL pointer, etc. \newline Each PBL pointer points to the physical address which contains an array …
1034 …which is passed to this function should be NULL. Note that ecore allocates by itself struct \textt…
1136 …BL pointer, etc. \newline Each PBL pointer points to the physical address which contains an array …
1159 …which is passed to this function should be NULL. Note that ecore allocates by itself struct \textt…
1217 …complete, and currently only details changes for iWARP. (Except for dcqcn which was already detail…
1226 Ecore per function context has a field “personality” which is set based on the protocol being iWARP…
1249 … number of rate limiters will be allocated during hardware initialization which can later be initi…
1274 … 64K, any number below this will result in the default window size being set which is 1MB \\ \hline
1279 …ery_device} -- this function returns a struct of type ecore\_rdma\_device which contains the capab…
1282 …rdma\_pf\_params allocates additional hardware resources (rate limiters ) which can later be used …
1285 …which is configured to work with a unique rate limiter. QPs that are opened after rate limiters ar…
1289 Unlike RoCE in which connection management is implemented completely in host, connection management…
1305 …is required. We define a structure called \texttt{ecore\_iwarp\_cm\_info} which will be passed bet…
1325 …ter to a callback function and callback context which will be used to indicate events to the drive…
1344 …which the ecore should listen on. Once a SYN packet is received on the ll2 interface, the ecore wi…
1346 …se. In addition a callback function and callback context will be provided which will be used by ec…
1360 …ring before calling this function. This function will send the MPA ramrod which will send a MPA re…
1488 …ecognized as pertaining to the iwarp offloaded connections. If an app tlv which matches this port …
1497 The LL2 is a simplified version of L2 for which both slowpath and fastpath flows reside in ecore, a…
1520 …\texttt{p\_connection\_handle} & Output parameter contains a handle which is used in future calls …
1534 …which the packet was written. \texttt{packet\_length} is the total packet length in bytes. \texttt…
1569 \myindex{SRIOV} is a PCIe functionality which allows Physical functions (also termed \myindex{PF}s)…
1575 on the VF side the upper driver will use the same API to access it’s ecore, which will in turn comm…
1583 The \textit{ecore\_dev} contains an \textit{sriov\_info} field, which is filled very early during i…
1585 …t it to `true'. However, if upper-driver utilizes a designated SW-channel which it can use instead…
1587 An additional important field is the \myindex{total\_vfs} which represents the maximal number of VF…
1590 …i.e., it's possible the first PF of a given VF will have an absolute vfid which is greater than ze…
1613 …passing from VF to PF, in which the VF can request the PF to either perform services for it or sup…
1617 …rmation is inaccessible to the VF. Thus the VF has an alternative flow by which it sends an ACQUIR…
1634 …\item Prior to VF activation, PF enables VF access to the HW-channel, which actually permits it to…
1635 …prepares a message on DMA-able memory, which also contains an address of an additional DMA-able me…
1643 …\item PF prepares an answer for the VF [success, failure, etc.] which might also contain informati…
1647 …_events}. It will return a bitmask of all the VFs belonging to the PF for which there's a message …
1658 The VF has a buffer named \myindex{bulletin-board} into which the PF posts messages.
1667 \myfunc{vf\_read\_bulletin}{vf_read_bulletin}, which checks for any changes.
1668 … boards], the upper-driver has a wide assortment of functions-per-feature which are defined in eco…
1678 …RE response sent from PF to VF, PF agrees upon the size of bulletin board which will be used [forw…
1684 …ite to a specific [standard] bit in the PCI function configuration space, which should result in t…
1692 The FLR flow is a complicated flow which involves Management firmware, storm firmware and driver al…
1700 …se VFs, and then call \myfunc{iov\_vf\_flr\_cleanup}{iov_vf_flr_cleanup}, which will continue the …
1703 …Unless \textit{ecore\_iov\_set\_vf\_to\_disable()} was called, in which case following the FLR tho…
1711 … message, process the parts it is aware of and be able to skip over parts which it doesn't recogni…
1738 … this test verifies the interrupt path. Ecore employs its most basic flow which exercises interrup…
1741 …les some of the memories in the device. Ecore employs its most basic flow which exercises memories…
1753 …uld call \myfunc{ptp\_enable}{ptp_enable} and then configure the required PTP filters which include