diff options
Diffstat (limited to 'docs/reference')
| -rw-r--r-- | docs/reference/isr_rules.rst | 2 | ||||
| -rw-r--r-- | docs/reference/speed_python.rst | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/reference/isr_rules.rst b/docs/reference/isr_rules.rst index 14010fb20..5e8d6ad61 100644 --- a/docs/reference/isr_rules.rst +++ b/docs/reference/isr_rules.rst @@ -209,7 +209,7 @@ issue a further interrupt. It then schedules a callback to process the data. Scheduled callbacks should comply with the principles of interrupt handler design outlined below. This is to avoid problems resulting from I/O activity and the modification of shared data which can arise in any code -which pre-empts the main program loop. +which preempts the main program loop. Execution time needs to be considered in relation to the frequency with which interrupts can occur. If an interrupt occurs while the previous callback is executing, a further instance of the callback will be queued diff --git a/docs/reference/speed_python.rst b/docs/reference/speed_python.rst index a660432f6..64fd9df6c 100644 --- a/docs/reference/speed_python.rst +++ b/docs/reference/speed_python.rst @@ -219,7 +219,7 @@ process known as garbage collection reclaims the memory used by these redundant objects and the allocation is then tried again - a process which can take several milliseconds. -There may be benefits in pre-empting this by periodically issuing `gc.collect()`. +There may be benefits in preempting this by periodically issuing `gc.collect()`. Firstly doing a collection before it is actually required is quicker - typically on the order of 1ms if done frequently. Secondly you can determine the point in code where this time is used rather than have a longer delay occur at random points, |