Skip to content

Conversation

@sanimej
Copy link

@sanimej sanimej commented Jul 13, 2017

When the gc_thresh3 value is reached kenel might remove existing neighbor entries. On an l3 miss try to reprogram the neighbor entry if the peer is valid.

Ideally the gc_thresh* values should be bumped up to avoid this issue. Since most customer are not aware of this setting #1789 increases it as part of the overlay driver init.

This patch is a best effort attempt to help if the user has for some reason reduced this value. neighbor entry programming will succeed if the arp table is currently not at gc_thresh3 value.

Signed-off-by: Santhosh Manohar santhosh@docker.com

neighbor entries. On an l3 miss try to reprogram the neighbor entry
if the peer is valid. Its a best effort attempt because if the arp
table is still at gc_thresh3 value, addition will fail.

Signed-off-by: Santhosh Manohar <santhosh@docker.com>
@sanimej
Copy link
Author

sanimej commented Jul 27, 2017

@mavenugo PTAL

@mavenugo
Copy link
Contributor

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants