| /illumos-gate/usr/src/tools/scripts/ |
| H A D | webrev.sh | 2135 file="$PF"
2137 file="$PDIR/$PF"
2141 cp $PWS/$PDIR/$PF $olddir/$PDIR/$PF
2185 cp $PWS/$PDIR/$PF $olddir/$PDIR/$PF
2210 rm -f $olddir/$PDIR/$PF
2211 cp $PWS/$PDIR/$PF $olddir/$PDIR/$PF
2220 typeset PF=$4
3031 PF=${PP##*/}
3050 PF=$F
3083 ofile=old/$PF
[all …]
|
| /illumos-gate/usr/src/cmd/printf/ |
| H A D | printf.c | 55 #define PF(f, func) do { \ macro
367 PF(start, p); in doformat()
374 PF(start, p); in doformat()
389 PF(f, val); in doformat()
391 PF(f, uval); in doformat()
403 PF(start, p); in doformat()
405 PF(start, (double)p); in doformat()
|
| /illumos-gate/usr/src/uts/common/io/qede/579xx/drivers/ecore/documentation/ |
| H A D | osal.txt | 407 to the PF, where the PF's answer should be written to `reply_addr'
413 for sending messages from VF to PF. This is called on the PF by
428 Called on the PF whenever the VF requests to configure a unicast
438 Called on the PF before starting a VF's vport, to check the
445 Called on the PF after succesfully starting a VF's vport,
467 Called on PF side to indicate MFW signaled some of the PF's
469 pending_flr field in the PF's iov information should be set
473 Called on PF side to indicate that VF has been cleaned, to allow
479 Called on the VF before sending acquire messgae to the PF,
508 Called on PF side to indicate the VF to PF TLV Request type send by VF in
[all …]
|
| H A D | ecore.tex | 992 \section{Start iSCSI PF}
1104 \section{Close iSCSI PF}
1123 \section{Start FCoE PF}
1200 \section{Close FCoE PF}
1231 \section{Init RDMA PF}
1609 \section{Message passing from VF to PF}
1624 …ide the ecore this will send a VPORT\_START TLV message from VF to PF, and that the PF will open t…
1642 \item ... PF processes the VF's request ...
1655 \section{Message Passing from PF to VF}
1656 The Message passing from VF to PF benefits from the PF's slowpath status-block, i.e., the ability o…
[all …]
|
| /illumos-gate/usr/src/uts/common/io/cxgbe/firmware/ |
| H A D | t4fw_cfg.txt | 40 # this "Unified PF" will need to have enough resources allocated to it
43 # severely limit the TotalVFs if we continue to use PF0 as the Unified PF
44 # or we'll need to move the Unified PF into the PF4-7 range since those
57 # managed via a single Unified PF and we want to accommodate scaling up
64 # for a total of 96 Ingress Queues and MSI-X Vectors on the Unified PF.
85 # If a Master PF Driver finds itself on a machine with different
86 # parameters, then the Master PF Driver is responsible for initializing
168 # PF" which many OS Drivers will use to manage most or all functions.
174 # Thus, the number of MSI-X Vectors assigned to the Unified PF will be less
245 # that up to 128 to make sure the Unified PF doesn't run out of resources.
[all …]
|
| H A D | t5fw_cfg.txt | 42 # managed via a single Unified PF and we want to accommodate scaling up
49 # for a total of 96 Ingress Queues and MSI-X Vectors on the Unified PF.
71 # If a Master PF Driver finds itself on a machine with different
72 # parameters, then the Master PF Driver is responsible for initializing
203 # PF" which many OS Drivers will use to manage most or all functions.
209 # Thus, the number of MSI-X Vectors assigned to the Unified PF will be less
270 # Adding all of the above Unified PF resource needs together: (NIC + OFLD +
280 # that up to 128 to make sure the Unified PF doesn't run out of resources.
302 # For PF4, the Unified PF, we give it an MSI-X Table Size as outlined above.
488 # access to one port (1 << PF). Note that because of limitations in the
|
| H A D | t6fw_cfg.txt | 42 # managed via a single Unified PF and we want to accommodate scaling up
49 # for a total of 96 Ingress Queues and MSI-X Vectors on the Unified PF.
71 # If a Master PF Driver finds itself on a machine with different
72 # parameters, then the Master PF Driver is responsible for initializing
220 # PF" which many OS Drivers will use to manage most or all functions.
226 # Thus, the number of MSI-X Vectors assigned to the Unified PF will be less
287 # Adding all of the above Unified PF resource needs together: (NIC + OFLD +
297 # that up to 128 to make sure the Unified PF doesn't run out of resources.
319 # For PF4, the Unified PF, we give it an MSI-X Table Size as outlined above.
506 # access to one port (1 << PF). Note that because of limitations in the
|
| /illumos-gate/usr/src/uts/common/io/qede/579xx/drivers/ecore/ |
| H A D | release.txt | 46 MTU settings on PF with VFs enumerated.
765 Change: Sync PF stop and MFW UNLOAD Request flow.
888 SBs between PF and its child-VFs.
993 another PF on the same engine.
2231 4. Problem: VF acquisition fails over a legacy PF.
2677 Change: Configure the correct TC to the PF.
2955 Change: PF enforces MAC limitation on VFs.
3567 default PF is used.
3570 default PF is used.
4126 3. Request: Add support for 16 PF AH emulation.
[all …]
|
| H A D | ecore_cxt.c | 694 &p_cli->pf_blks[CDUT_FL_SEG_BLK(i, PF)]); in ecore_cxt_cfg_ilt_compute()
1548 (p_cli->pf_blks[CDUT_FL_SEG_BLK(i, PF)].start_line - in ecore_cdu_init_pf()
2329 p_fl_seg = &p_cli->pf_blks[CDUT_FL_SEG_BLK(seg, PF)]; in ecore_cxt_get_tid_mem_info()
2620 p_seg = &p_cli->pf_blks[CDUT_FL_SEG_BLK(seg, PF)]; in ecore_cxt_get_task_ctx()
|
| /illumos-gate/usr/src/uts/common/io/e1000api/ |
| H A D | README.new | 208 Intel(R) PRO/1000 PF Quad Port Server Adapter
209 Intel(R) PRO/1000 PF Server Adapter
210 Intel(R) PRO/1000 PF Network Connection
211 Intel(R) PRO/1000 PF Dual Port Server Adapter
|
| /illumos-gate/usr/src/pkg/manifests/ |
| H A D | driver-network-sfxge.p5m | 21 # pci1924,913 - Medford (PF, Uninitialized)
|
| /illumos-gate/usr/src/data/zoneinfo/ |
| H A D | zone.tab.txt | 309 PF -1732-14934 Pacific/Tahiti Society Islands
310 PF -0900-13930 Pacific/Marquesas Marquesas Islands
311 PF -2308-13457 Pacific/Gambier Gambier Islands
|
| H A D | zone_sun.tab | 332 PF -1732-14934 Pacific/Tahiti - Society Islands
333 PF -0900-13930 Pacific/Marquesas - Marquesas Islands
334 PF -2308-13457 Pacific/Gambier - Gambier Islands
|
| H A D | country.tab | 205 PF French Polynesia
|
| /illumos-gate/usr/src/boot/i386/btx/btx/ |
| H A D | btx.S | 339 push $0xe # Int 0xe: #PF
|
| /illumos-gate/usr/src/uts/common/io/qede/579xx/hsi/mcp/ |
| H A D | nvm_meta.txt | 165 74,name "Number of VFs per PF" 74,group_name "VF" 74,entity_name "func" 74,struct_name "nvm_cfg1" 7…
318 232,name "PF Mapping" 232,group_name "features" 232,entity_name "glob" 232,struct_name "nvm_cfg1" 2…
|
| /illumos-gate/usr/src/uts/common/io/bnxe/577xx/drivers/common/lm/vf/channel_vf/ |
| H A D | lm_vf.c | 2682 Windows8 PF executes clear IGU block on VM initialization. Must be checked for Linux PF. in lm_vf_chip_init()
|
| /illumos-gate/usr/src/data/hwdata/ |
| H A D | pci.ids | 22033 7102 NPS-400 network interface PF
22036 7122 NPS-600 network interface PF
26259 8003 RCEC PF
26958 0c10 Compass C10 PF
29121 8086 005a PRO/1000 PF Dual Port Server Adapter
29122 8086 115f PRO/1000 PF Dual Port Server Adapter
29123 8086 125f PRO/1000 PF Dual Port Server Adapter
29124 8086 135f PRO/1000 PF Dual Port Server Adapter
29184 8086 1084 PRO/1000 PF Server Adapter
29185 8086 1085 PRO/1000 PF Server Adapter
[all …]
|
| H A D | usb.ids | 3633 1013 PF-500
|
| /illumos-gate/usr/src/data/terminfo/ |
| H A D | termcap.src | 2715 # scheme for PF keys.
9108 # smkx programs the SYS PF keys to send a set sequence.
9111 # when pressed in SYS PF mode.
9143 # Note that this mode permits programming USER PF KEYS and labels
11559 :do=^^PB:ho=^^PF:i1=\022\003\036P@1:i2=\036Fz0:kC=^^PH:\
11560 :kE=^^PE:kd=^^PB:kh=^^PF:kl=^^PD:kr=^^PC:ku=^^PA:le=^^PD:\
18093 # :so=^P\s\002^PF: works but won't go away without dynamite :se=^P\s\0:.
|
| H A D | terminfo.src | 3065 # scheme for PF keys.
10225 # smkx programs the SYS PF keys to send a set sequence.
10228 # when pressed in SYS PF mode.
10270 # Note that this mode permits programming USER PF KEYS and labels
13055 el=^^PE, home=^^PF, hpa=\020%p1%c\177, ht=^I, ind=^J,
13058 kcuf1=^^PC, kcuu1=^^PA, kel=^^PE, khome=^^PF, kprt=^^P0,
20278 # <smso=^P\s\002^PF> works but won't go away without dynamite <rmso=^P\s\0>.
|