Delete duplicate words from kernel docs

	So if you need to wait for both an RCU grace period and for

	all pre-existing call_rcu() callbacks, you will need to execute

	both rcu_barrier() and synchronize_rcu(), if necessary, using

	something like workqueues to to execute them concurrently.

	something like workqueues to execute them concurrently.

	See rcubarrier.rst for more information.

	rcu_access_pointer(p):

		Return the value of the pointer and omit all barriers,

		but retain the compiler constraints that prevent duplicating

		or coalescsing.  This is useful when when testing the

		or coalescsing.  This is useful when testing the

		value of the pointer itself, for example, against NULL.

The rcu_dereference_check() check expression can be any boolean

The byte swap instructions operate on the destination register

only and do not use a separate source register or immediate value.

The 1-bit source operand field in the opcode is used to to select what byte

The 1-bit source operand field in the opcode is used to select what byte

order the operation convert from or to:

  =========  =====  =================================================

  Because the default sort key above is 'hitcount', the above shows a

  the list of call_sites by increasing hitcount, so that at the bottom

  we see the functions that made the most kmalloc calls during the

  run.  If instead we we wanted to see the top kmalloc callers in

  run.  If instead we wanted to see the top kmalloc callers in

  terms of the number of bytes requested rather than the number of

  calls, and we wanted the top caller to appear at the top, we can use

  the 'sort' parameter, along with the 'descending' modifier::

        [root@f32 ~]# cd /sys/kernel/tracing/

        [root@f32 tracing]# echo timerlat > current_tracer

It is possible to follow the trace by reading the trace trace file::

It is possible to follow the trace by reading the trace file::

  [root@f32 tracing]# cat trace

  # tracer: timerlat