[PATCH 1/7] future/tm: Remove unnecessary spaces
SeongJae Park <[email protected]>
| Newsgroups | org.kernel.vger.perfbook |
|---|---|
| Message-ID | <[email protected]> |
A couple of sentences in future/tm.tex are having two spaces between two words unnecessarily. Remove one. Signed-off-by: SeongJae Park <[email protected]> --- future/tm.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/future/tm.tex b/future/tm.tex index e6985099..1de900b8 100644 --- a/future/tm.tex +++ b/future/tm.tex @@ -126,7 +126,7 @@ Here are some options for handling of I/O within transactions: However, special handling is required in cases where multiple record-oriented output streams are merged onto a single file from multiple processes, as might be done using the ``a+'' - option to \co{fopen()} or the \co{O_APPEND} flag to \co{open()}. + option to \co{fopen()} or the \co{O_APPEND} flag to \co{open()}. In addition, as will be seen in the next section, common networking operations cannot be handled via buffering. \item Prohibit I/O within transactions, so that any attempt to execute @@ -240,7 +240,7 @@ Here are some options available to TM: back, with consequent degradation of performance and scalability. This approach nevertheless might be valuable given long-running transactions ending with an RPC\@. - This approach must still restrict manual transaction-abort + This approach must still restrict manual transaction-abort operations. \item Identify special cases where the RPC response may be moved out of the transaction, and then proceed using techniques similar -- 2.17.1