Skip to content

Commit 97686dd

Browse files
committed
Fix _cn to _en, and ##### to short
1 parent 56a90b7 commit 97686dd

File tree

5 files changed

+24
-24
lines changed

5 files changed

+24
-24
lines changed

docs/dev_guides/custom_device_docs/custom_device_example_en.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Then, the plug-in should fill in its basic information and version number, which
5959
- params->device_type : the appellation of the device backend. If there is another plug-in with the same name, the runtime will not be registered.
6060
- params->sub_device_type : the appellation of the sub-type of the device backend
6161
62-
Finally, some callback APIs in params->interface should be filled by the plug-in (At least the required APIs should be implemented, or the runtime will not be registered otherwise). Thus, the custom runtime can be initialized. For details of the APIS, please refer to [Custom Runtime Document](./custom_runtime_cn.html)。
62+
Finally, some callback APIs in params->interface should be filled by the plug-in (At least the required APIs should be implemented, or the runtime will not be registered otherwise). Thus, the custom runtime can be initialized. For details of the APIS, please refer to [Custom Runtime Document](./custom_runtime_en.html)。
6363
6464
```c++
6565
static size_t global_total_mem_size = 1 * 1024 * 1024 * 1024UL;

docs/dev_guides/custom_device_docs/custom_kernel_docs/cpp_api_en.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
#############
1+
#############################
22
Kernel Implementation APIs
3-
#############
3+
#############################
44

55
The custom kernel-function implementation mainly depends on two parts: 1.APIs released by PaddlePaddle, including the context API, the tensor API, and the exception API; 2. APIs of the device encapsulation library. And the C++ API of PaddlePaddle has been released by the header file.
66

docs/dev_guides/custom_device_docs/custom_kernel_en.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@ The custom kernel is the implementation of corresponding operators of the kernel
66
The implementation of the custom kernel is based on the public kernel statement of PaddlePaddle, and public C++ API and register macro.
77

88

9-
- `Kernel function statement <./custom_kernel_docs/kernel_declare_cn.html>`_ : to introduce the kernel statement of PaddlePaddle
10-
- `Kernel implementation API <./custom_kernel_docs/cpp_api_cn.html>`_ : to introduce the C++ API required in the implementation of the custom function.
11-
- `Kernel register API <./custom_kernel_docs/register_api_cn.html>`_ : to introduce the register macro of the custom kernel.
9+
- `Kernel function statement <./custom_kernel_docs/kernel_declare_en.html>`_ : to introduce the kernel statement of PaddlePaddle
10+
- `Kernel implementation API <./custom_kernel_docs/cpp_api_en.html>`_ : to introduce the C++ API required in the implementation of the custom function.
11+
- `Kernel register API <./custom_kernel_docs/register_api_en.html>`_ : to introduce the register macro of the custom kernel.
1212

1313

1414
.. toctree::
1515
:hidden:
1616

17-
custom_kernel_docs/kernel_declare_cn.md
18-
custom_kernel_docs/cpp_api_cn.rst
19-
custom_kernel_docs/register_api_cn.md
17+
custom_kernel_docs/kernel_declare_en.md
18+
custom_kernel_docs/cpp_api_en.rst
19+
custom_kernel_docs/register_api_en.md

docs/dev_guides/custom_device_docs/custom_runtime_en.rst

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
#############
1+
#############################
22
Custom Runtime
3-
#############
3+
#############################
44

55
Custom Runtime offers a new method to register the runtime of new devices via plug-ins. Responsible for the management of PaddlePaddle devices and Runtime/Driver API, DeviceManager provides a uniform API for the framework to invoke device capabilities, offers a series of APIs to register Custom Runtime, and ensure that the binary system is compatible through C API. The APIs can be found in `device_ext.h <https://github.com/PaddlePaddle/Paddle/blob/develop/paddle/phi/backends/device_ext.h>`_ . Developers can add custom runtime for PaddlePaddle only by implementing these APIs.
66

7-
- `Data type <./runtime_data_type_cn.html>`_ : to introduce definitions of data types of custom runtime.
8-
- `Device API <./device_api_cn.html>`_ : to introduce definitions and functions of Device APIs.
9-
- `Memory API <./memory_api_cn.html>`_ : to introduce definitions and functions of Memory APIs.
10-
- `Stream API <./stream_api_cn.html>`_ : to introduce definitions and functions of Stream APIs.
11-
- `Event API <./event_api_cn.html>`_ : to introduce definitions and functions of Event APIs.
7+
- `Data type <./runtime_data_type_en.html>`_ : to introduce definitions of data types of custom runtime.
8+
- `Device API <./device_api_en.html>`_ : to introduce definitions and functions of Device APIs.
9+
- `Memory API <./memory_api_en.html>`_ : to introduce definitions and functions of Memory APIs.
10+
- `Stream API <./stream_api_en.html>`_ : to introduce definitions and functions of Stream APIs.
11+
- `Event API <./event_api_en.html>`_ : to introduce definitions and functions of Event APIs.
1212

1313

1414
Device APIs
@@ -136,9 +136,9 @@ Event APIs
136136
.. toctree::
137137
:hidden:
138138

139-
runtime_data_type_cn.md
140-
device_api_cn.md
141-
memory_api_cn.md
142-
stream_api_cn.md
143-
event_api_cn.md
139+
runtime_data_type_en.md
140+
device_api_en.md
141+
memory_api_en.md
142+
stream_api_en.md
143+
event_api_en.md
144144

docs/dev_guides/custom_device_docs/index_en.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
1-
####################
1+
#############################
22
Custom Device Access Guide
3-
####################
3+
#############################
44

55
The custom device access decouples the framework from the device and makes it available to extend the backend of the PaddlePaddle device via plug-ins. In this way, developers can make a plug-in for PaddlePaddle only by implementing the standard API and compiling it into a dynamic-link library, instead of by modifying the code of PaddlePaddle. Now it is easier to develop hardware backends for PaddlePaddle.
66

77
The custom device access is composed of custom runtime and custom kernel. With the two modules, users can connect new custom devices to PaddlePaddle according to their own needs.
88

99
- `Custom Runtime <./custom_runtime_en.html>`_ : Introduction of custom runtime of the PaddlePaddle framework
1010
- `Custom Kernel <./custom_kernel_en.html>`_ : Introduction of custom kernel of the PaddlePaddle framework
11-
- `Example of Device Access <./custom_kernel_en.html>`_ : To demonstrate how to connect new custom devices to PaddlePaddle
11+
- `Example of Device Access <./custom_device_example_en.html>`_ : To demonstrate how to connect new custom devices to PaddlePaddle
1212

1313
.. toctree::
1414
:hidden:

0 commit comments

Comments
 (0)