d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

tcp_hpts: Correct some typos in source code comments

Browse Source 
- s/occured/occurred/
- s/the the/the/

MFC after:	3 days
This commit is contained in:
Gordon Bergling 2022-09-04 12:47:49 +02:00
parent 4d89e2018c
commit d07a501876
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
sys/netinet/tcp_hpts.c
View File

@ -1341,7 +1341,7 @@ tcp_hptsi(struct tcp_hpts_entry *hpts, int from_callout)
* goes off and sees the mis-match. We
* simply correct it here and the CPU will
* switch to the new hpts nextime the tcb
* gets added to the the hpts (not this one)
* gets added to the hpts (not this one)
* :-)
*/
tcp_set_hpts(inp);
@ -1376,7 +1376,7 @@ tcp_hptsi(struct tcp_hpts_entry *hpts, int from_callout)
* than the previous inp) and there no
* assurance that ninp was not pulled while
* we were processing inp and freed. If this
* occured it could mean that either:
* occurred it could mean that either:
*
* a) Its NULL (which is fine we won't go
* here) <or> b) Its valid (which is cool we

2
sys/netinet/tcp_hpts.h
View File

@ -129,7 +129,7 @@ bool tcp_in_hpts(struct inpcb *);
* it to be 1 (so you wont call output) it may be transitioning
* to 0 (by the hpts). That will be fine since that will just
* mean an extra call to tcp_output that most likely will find
* the call you executed (when the mis-match occured) will have
* the call you executed (when the mis-match occurred) will have
* put the TCB back on the hpts and it will return. If your
* call did not add it back to the hpts then you will either
* over-send or the cwnd will block you from sending more.