doc:networking: Fix typo in documentation/networking (3dd17ede) · Commits · e / devices / android_kernel_oneplus_sm7250

Documentation/networking/ifenslave.c

+1 −1

Original line number	Original line	Diff line number	Diff line
	@@ -501,7 +501,7 @@ int main(int argc, char *argv[])

	static short mif_flags;		static short mif_flags;

	/* Get the inteface configuration from the kernel. */		/* Get the interface configuration from the kernel. */
	static int if_getconfig(char *ifname)		static int if_getconfig(char *ifname)
	{		{
	struct ifreq ifr;		struct ifreq ifr;

Documentation/networking/ip-sysctl.txt

+1 −1

Original line number	Original line	Diff line number	Diff line
	@@ -183,7 +183,7 @@ tcp_early_retrans - INTEGER
	for triggering fast retransmit when the amount of outstanding data is		for triggering fast retransmit when the amount of outstanding data is
	small and when no previously unsent data can be transmitted (such		small and when no previously unsent data can be transmitted (such
	that limited transmit could be used). Also controls the use of		that limited transmit could be used). Also controls the use of
	Tail loss probe (TLP) that converts RTOs occuring due to tail		Tail loss probe (TLP) that converts RTOs occurring due to tail
	losses into fast recovery (draft-dukkipati-tcpm-tcp-loss-probe-01).		losses into fast recovery (draft-dukkipati-tcpm-tcp-loss-probe-01).
	Possible values:		Possible values:
	0 disables ER		0 disables ER

Documentation/networking/netlink_mmap.txt

+7 −7

Original line number	Original line	Diff line number	Diff line
	@@ -54,7 +54,7 @@ it will use an allocated socket buffer as usual and the contents will be
	copied to the ring on transmission, nullifying most of the performance gains.		copied to the ring on transmission, nullifying most of the performance gains.
	Dumps of kernel databases automatically support memory mapped I/O.		Dumps of kernel databases automatically support memory mapped I/O.

	Conversion of the transmit path involves changing message contruction to		Conversion of the transmit path involves changing message construction to
	use memory from the TX ring instead of (usually) a buffer declared on the		use memory from the TX ring instead of (usually) a buffer declared on the
	stack and setting up the frame header approriately. Optionally poll() can		stack and setting up the frame header approriately. Optionally poll() can
	be used to wait for free frames in the TX ring.		be used to wait for free frames in the TX ring.
	@@ -65,8 +65,8 @@ Structured and definitions for using memory mapped I/O are contained in
	RX and TX rings		RX and TX rings
	----------------		----------------

	Each ring contains a number of continous memory blocks, containing frames of		Each ring contains a number of continuous memory blocks, containing frames of
	fixed size dependant on the parameters used for ring setup.		fixed size dependent on the parameters used for ring setup.

	Ring: [ block 0 ]		Ring: [ block 0 ]
	[ frame 0 ]		[ frame 0 ]
	@@ -80,7 +80,7 @@ Ring: [ block 0 ]
	[ frame 2 * n + 1 ]		[ frame 2 * n + 1 ]

	The blocks are only visible to the kernel, from the point of view of user-space		The blocks are only visible to the kernel, from the point of view of user-space
	the ring just contains the frames in a continous memory zone.		the ring just contains the frames in a continuous memory zone.

	The ring parameters used for setting up the ring are defined as follows:		The ring parameters used for setting up the ring are defined as follows:

	@@ -91,7 +91,7 @@ struct nl_mmap_req {
	unsigned int nm_frame_nr;		unsigned int nm_frame_nr;
	};		};

	Frames are grouped into blocks, where each block is a continous region of memory		Frames are grouped into blocks, where each block is a continuous region of memory
	and holds nm_block_size / nm_frame_size frames. The total number of frames in		and holds nm_block_size / nm_frame_size frames. The total number of frames in
	the ring is nm_frame_nr. The following invariants hold:		the ring is nm_frame_nr. The following invariants hold:

	@@ -113,8 +113,8 @@ Some parameters are constrained, specifically:

	- nm_frame_nr must equal the actual number of frames as specified above.		- nm_frame_nr must equal the actual number of frames as specified above.

	When the kernel can't allocate phsyically continous memory for a ring block,		When the kernel can't allocate phsyically continuous memory for a ring block,
	it will fall back to use physically discontinous memory. This might affect		it will fall back to use physically discontinuous memory. This might affect
	performance negatively, in order to avoid this the nm_frame_size parameter		performance negatively, in order to avoid this the nm_frame_size parameter