linux内核文件翻译

Chinese translated version of Documentation/namespaces/resource-control.txt

If you have any comment or update to the content, please contact the

original document maintainer directly. However, if you have a problem

communicating in English you can also ask the Chinese maintainer for

help. Contact the Chinese maintainer if this translation is outdated

or if there is a problem with the translation.

Chinese maintainer: 田雨 479103577@qq.com

---------------------------------------------------------------------

Documentation/namespaces/resource-control.txt 的中文翻译

如果想评论或更新本文的内容，请直接联系原文档的维护者。如果你使用英文

交流有困难的话，也可以向中文版维护者求助。如果本翻译更新不及时或者翻

译存在问题，请联系中文版维护者。

中文版维护者： 田雨 479103577@qq.com

中文版翻译者： 田雨 479103577@qq.com

中文版校译者： 田雨 479103577@qq.com

1 The device-mapper uevent code adds the capability to device-mapper to create

2 and send kobject uevents (uevents). Previously device-mapper events were only

3 available through the ioctl interface. The advantage of the uevents interface

4 is the event contains environment attributes providing increased context for

5 the event avoiding the need to query the state of the device-mapper device after

6 the event is received.

7 创建的device-mapper UEVENT代码添加能力的device-mapper

，并发送kobject的uevents（uevents）。此前的device-mapper事件

可通过ioctl接口。的uevents接口的优点

事件包含提供更多的上下文环境属性

事件后避免需要查询的device-mapper设备的状态

接收到事件。

8 There are two functions currently for device-mapper events. The first function

9 listed creates the event and the second function sends the event(s).

10 目前的device-mapper事件有两个函数。第一个函数

上市的创建事件，而第二个函数发送事件（次）。

11 void dm_path_uevent(enum dm_uevent_type event_type, struct dm_target *ti,

12 const char *path, unsigned nr_valid_paths)

13 无效dm_path_uevent（枚举，结构dm_target* TI dm_uevent_type EVENT_TYPE，

为const char*路径，无符号nr_valid_paths），

14 void dm_send_uevents(struct list_head *events, struct kobject *kobj)

15 的无效dm_send_uevents（结构的list_head*事件，结构的kobject* kobj的）

16

17 The variables added to the uevent environment are:

18 添加的uevent环境的变量是：

19 Variable Name: DM_TARGET

20 Uevent Action(s): KOBJ_CHANGE

21 Type: string

22 Description:

23 Value: Name of device-mapper target that generated the event.

24 变量名：DM_TARGET的

UEVENT行动（S）：KOBJ_CHANGE

类型：string

说明：

价值：设备映射目标产生的事件的名称。

25 Variable Name: DM_ACTION

26 Uevent Action(s): KOBJ_CHANGE

27 Type: string

28 Description:

29 Value: Device-mapper specific action that caused the uevent action.

30 PATH_FAILED - A path has failed.

31 PATH_REINSTATED - A path has been reinstated.

32 变量名：DM_ACTION的

UEVENT行动（S）：KOBJ_CHANGE

类型：string

说明：

价值：设备映射引起的uevent行动的具体行动。

PATH_FAILED - 路径已失败。

PATH_REINSTATED - ，路径已经恢复。

33 Variable Name: DM_SEQNUM

34 Uevent Action(s): KOBJ_CHANGE

35 Type: unsigned integer

36 Description: A sequence number for this specific device-mapper device.

37 Value: Valid unsigned integer range.

38 变量名：DM_SEQNUM

UEVENT行动（S）：KOBJ_CHANGE

类型：无符号整数

说明：为这个特定的device-mapper设备的序列号。

价值：有效的无符号整数的范围。

39 Variable Name: DM_PATH

40 Uevent Action(s): KOBJ_CHANGE

41 Type: string

42 Description: Major and minor number of the path device pertaining to this

43 event.

44 Value: Path name in the form of "Major:Minor"

45变量名：DM_PATH

UEVENT行动（S）：KOBJ_CHANGE

类型：string

说明：主要和次要路径设备有关

事件。

值：路径名“主要的形式：次要”

46 Variable Name: DM_NR_VALID_PATHS

47 Uevent Action(s): KOBJ_CHANGE

48 Type: unsigned integer

49 Description:

50 Value: Valid unsigned integer range.

51 变量名：DM_NR_VALID_PATHS

UEVENT行动（S）：KOBJ_CHANGE

类型：无符号整数

说明：

价值：有效的无符号整数的范围。

52 Variable Name: DM_NAME

53 Uevent Action(s): KOBJ_CHANGE

54 Type: string

55 Description: Name of the device-mapper device.

56 Value: Name

57 变量名：DM_NAME的

UEVENT行动（S）：KOBJ_CHANGE

类型：string

说明：设备映射设备的名称。

价值：产品名称

58 Variable Name: DM_UUID

59 Uevent Action(s): KOBJ_CHANGE

60 Type: string

61 Description: UUID of the device-mapper device.

62 Value: UUID. (Empty string if there isn't one.)

63 变量名：DM_UUID

UEVENT行动（S）：KOBJ_CHANGE

类型：string

说明：设备映射设备的UUID。

值：UUID。 （如果没有一个空字符串）。

64 An example of the uevents generated as captured by udevmonitor is shown

65 below.

66 所示的产生如由udevmonitor可捕获uevents的一个例子

以下。

67 1.) Path failure.

68 UEVENT[1192521009.711215] change@/block/dm-3

69 ACTION=change

70 DEVPATH=/block/dm-3

71 SUBSYSTEM=block

72 DM_TARGET=multipath

73 DM_ACTION=PATH_FAILED

74 DM_SEQNUM=1

75 DM_PATH=8:32

76 DM_NR_VALID_PATHS=0

77 DM_NAME=mpath2

78 DM_UUID=mpath-35333333000002328

79 MINOR=3

80 MAJOR=253

81 SEQNUM=1130

82

83 2.) Path reinstate.83 路径恢复。

84 UEVENT[1192521132.989927] change@/block/dm-3

85 ACTION=change

86 DEVPATH=/block/dm-3

87 SUBSYSTEM=block

88 DM_TARGET=multipath

89 DM_ACTION=PATH_REINSTATED

90 DM_SEQNUM=2

91 DM_PATH=8:32

92 DM_NR_VALID_PATHS=1

93 DM_NAME=mpath2

94 DM_UUID=mpath-35333333000002328

95 MINOR=3

96 MAJOR=253

97 SEQNUM=1131