(search_binary_handler+0x80/0x1bc)
[] (search_binary_handler) from []
(do_execveat_common+0x4f0/0x6dc)
[] (do_execveat_common) from []
(SyS_execve+0x30/0x38)
[] (SyS_execve) from []
(__sys_trace_return+0x0/0x2c)
CPU1: stopping
Best Regards,
Ulf Samuelsson
On 04/22/2015 12:46 PM, YOSHIFUJI Hideaki wrote:
Ulf Samuelsson wrote:
On 04/21/2015 05:58 AM, YOSHIFUJI Hideaki wrote:
Ulf Samuelsson wrote:
How many neighbors do you want to maintain?
I guess you have to increase the number of gc_thresh1.
The current use cases have up to 2048 entries
On 04/21/2015 05:58 AM, YOSHIFUJI Hideaki wrote:
Ulf Samuelsson wrote:
How many neighbors do you want to maintain?
I guess you have to increase the number of gc_thresh1.
The current use cases have up to 2048 entries.
This is expected to grow in the future.
The 3.4 kernel used in the system
On 04/20/2015 04:33 AM, YOSHIFUJI Hideaki wrote:
Hi,
Ulf Samuelsson wrote:
From RFC2461:
| REACHABLE Roughly speaking, the neighbor is known to have been
| reachable recently (within tens of seconds ago).
:
| STALE The neighbor is no longer known to be
On 04/16/2015 07:16 AM, YOSHIFUJI Hideaki wrote:
Hi,
Ulf Samuelsson wrote:
The desired functionality is that if communication stops,
you want to send out ARP probes, before the entry is deleted.
The current (pseudo) code of the neigh timer is:
if (state & NUD_REACHABLE) {
le in Kconfig
to allow the selection of functionality.
I am told that setting stuff using sysctl has a performance penalty, when
interfaces are dynamically created and deleted in hundreds.
Best Regards,
Ulf Samuelsson
On 04/10/2015 10:26 AM, Ulf Samuelsson wrote:
On 03/12/2015 07:26 PM, David M
