Skip to content

Commit b0cb56b

Browse files
authored
Merge pull request #187122 from steveesp/master
AccelNet documentation refactor
2 parents 12965da + 6a7fa61 commit b0cb56b

8 files changed

+387
-142
lines changed

articles/aks/reduce-latency-ppg.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Proximity placement groups are a node pool concept and associated with each indi
4545

4646
The following example uses the [az group create][az-group-create] command to create a resource group named *myResourceGroup* in the *centralus* region. An AKS cluster named *myAKSCluster* is then created using the [az aks create][az-aks-create] command.
4747

48-
Accelerated networking greatly improves networking performance of virtual machines. Ideally, use proximity placement groups in conjunction with accelerated networking. By default, AKS uses accelerated networking on [supported virtual machine instances](../virtual-network/create-vm-accelerated-networking-cli.md?toc=/azure/virtual-machines/linux/toc.json#limitations-and-constraints), which include most Azure virtual machine with two or more vCPUs.
48+
Accelerated networking greatly improves networking performance of virtual machines. Ideally, use proximity placement groups in conjunction with accelerated networking. By default, AKS uses accelerated networking on [supported virtual machine instances](../virtual-network/accelerated-networking-overview.md?toc=/azure/virtual-machines/linux/toc.json#limitations-and-constraints), which include most Azure virtual machine with two or more vCPUs.
4949

5050
Create a new AKS cluster with a proximity placement group associated to the first system node pool:
5151

@@ -134,4 +134,4 @@ az group delete --name myResourceGroup --yes --no-wait
134134
[az-aks-nodepool-add]: /cli/azure/aks/nodepool#az_aks_nodepool_add
135135
[az-aks-create]: /cli/azure/aks#az_aks_create
136136
[az-group-create]: /cli/azure/group#az_group_create
137-
[az-group-delete]: /cli/azure/group#az_group_delete
137+
[az-group-delete]: /cli/azure/group#az_group_delete

articles/service-fabric/how-to-managed-cluster-networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -587,7 +587,7 @@ To configure bring your own load balancer:
587587

588588
<a id="accelnet"></a>
589589
## Enable Accelerated Networking (preview)
590-
Accelerated networking enables single root I/O virtualization (SR-IOV) to a virtual machine scale set VM that is the underlying resource for node types. This high-performance path bypasses the host from the data path, which reduces latency, jitter, and CPU utilization for the most demanding network workloads. Service Fabric managed cluster node types can be provisioned with Accelerated Networking on [supported VM SKUs](../virtual-machines/sizes.md). Reference this [limitations and constraints](../virtual-network/create-vm-accelerated-networking-powershell.md#limitations-and-constraints) for additional considerations.
590+
Accelerated networking enables single root I/O virtualization (SR-IOV) to a virtual machine scale set VM that is the underlying resource for node types. This high-performance path bypasses the host from the data path, which reduces latency, jitter, and CPU utilization for the most demanding network workloads. Service Fabric managed cluster node types can be provisioned with Accelerated Networking on [supported VM SKUs](../virtual-machines/sizes.md). Reference this [limitations and constraints](../virtual-network/accelerated-networking-overview.md#limitations-and-constraints) for additional considerations.
591591

592592
* Note that Accelerated Networking is supported on most general purpose and compute-optimized instance sizes with 2 or more vCPUs. On instances that support hyperthreading, Accelerated Networking is supported on VM instances with 4 or more vCPUs.
593593

articles/site-recovery/azure-vm-disaster-recovery-with-accelerated-networking.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,6 @@ If you have enabled Accelerated Networking on the source virtual machine after e
8181
The above process should also be followed for existing replicated virtual machines, that did not previously have Accelerated Networking enabled automatically by Site Recovery.
8282

8383
## Next steps
84-
- Learn more about [benefits of Accelerated Networking](../virtual-network/create-vm-accelerated-networking-powershell.md#benefits).
85-
- Learn more about limitations and constraints of Accelerated Networking for [Windows virtual machines](../virtual-network/create-vm-accelerated-networking-powershell.md#limitations-and-constraints) and [Linux virtual machines](../virtual-network/create-vm-accelerated-networking-cli.md#limitations-and-constraints).
86-
- Learn more about [recovery plans](site-recovery-create-recovery-plans.md) to automate application failover.
84+
- Learn more about [benefits of Accelerated Networking](../virtual-network/accelerated-networking-overview.md#benefits).
85+
- Learn more about limitations and constraints of Accelerated Networking for [Windows virtual machines](../virtual-network/accelerated-networking-overview.md#limitations-and-constraints) and [Linux virtual machines](../virtual-network/accelerated-networking-overview.md#limitations-and-constraints).
86+
- Learn more about [recovery plans](site-recovery-create-recovery-plans.md) to automate application failover.

0 commit comments

Comments
 (0)