From: David Miller <davem@davemloft.net>
To: sowmini.varadhan@oracle.com
Cc: stsp@list.ru, netdev@vger.kernel.org, alexander.duyck@gmail.com
Subject: Re: Q: bad routing table cache entries
Date: Tue, 12 Jan 2016 15:33:35 -0500 (EST) [thread overview]
Message-ID: <20160112.153335.213439668062764562.davem@davemloft.net> (raw)
In-Reply-To: <20160112144725.GA30240@oracle.com>
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Date: Tue, 12 Jan 2016 09:47:25 -0500
> On (01/12/16 17:40), Stas Sergeev wrote:
>> Updated testing results:
>> After I disabled shared_media not only for "all", but
>> also for _all_ interfaces individually, the problem seem to
>> have stopped. So thanks for these hints.
>> Now, as the media is actually really shared (same NIC/cable),
>> I just wonder what's going on here.
>
> I dont know the history of the shared_media tunable (or
> the rationale behind the default) - I was just reading out the
> code - perhaps someone on the list who has the history can share
> the motivation behind this tunable.
Most of the choices for defaults for ipv4 routing and ARP behavior
are motivated by two things:
1) host based addressing model
2) increasing the chance of successful communication with peers
next prev parent reply other threads:[~2016-01-12 20:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 10:54 Q: bad routing table cache entries Stas Sergeev
2015-12-29 11:58 ` Sowmini Varadhan
2015-12-29 12:06 ` Stas Sergeev
2015-12-29 12:32 ` Sowmini Varadhan
2015-12-29 12:43 ` Stas Sergeev
2015-12-29 13:19 ` Stas Sergeev
2015-12-29 15:22 ` Sowmini Varadhan
2015-12-29 15:38 ` Stas Sergeev
2015-12-29 17:40 ` Stas Sergeev
2015-12-30 12:42 ` Stas Sergeev
2015-12-30 14:17 ` Eric Dumazet
2015-12-30 17:56 ` David Miller
2016-01-04 1:05 ` Sowmini Varadhan
2016-01-04 1:32 ` Stas Sergeev
2016-01-04 17:23 ` Stas Sergeev
2016-01-12 14:40 ` Stas Sergeev
2016-01-12 14:47 ` Sowmini Varadhan
2016-01-12 20:33 ` David Miller [this message]
2016-01-12 15:34 ` Hannes Frederic Sowa
2016-01-12 15:52 ` Hannes Frederic Sowa
2016-01-12 16:03 ` Stas Sergeev
2016-01-12 16:10 ` Hannes Frederic Sowa
2016-01-12 16:42 ` Stas Sergeev
2016-01-12 16:56 ` Stas Sergeev
2016-01-12 17:06 ` Hannes Frederic Sowa
2016-01-12 17:18 ` Stas Sergeev
2016-01-12 17:26 ` Hannes Frederic Sowa
2016-01-12 17:33 ` Stas Sergeev
2016-01-12 17:47 ` Hannes Frederic Sowa
2016-01-12 20:43 ` Stas Sergeev
2016-01-12 22:26 ` Hannes Frederic Sowa
2016-01-12 22:57 ` Stas Sergeev
2016-01-12 23:07 ` Hannes Frederic Sowa
2016-01-13 12:59 ` Stas Sergeev
2016-01-12 17:41 ` Stas Sergeev
2016-01-12 15:57 ` Stas Sergeev
-- strict thread matches above, loose matches on Subject: below --
2015-12-28 15:26 Stas Sergeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160112.153335.213439668062764562.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.duyck@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.com \
--cc=stsp@list.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.