From: Stephen Hemminger <stephen@networkplumber.org>
To: Aleksey Shumnik <ashumnik9@gmail.com>
Cc: netdev@vger.kernel.org, waltje@uwalt.nl.mugnet.org,
Jakub Kicinski <kuba@kernel.org>,
gw4pts@gw4pts.ampr.org, kuznet@ms2.inr.ac.ru,
"willemdebruijn.kernel@gmail.com"
<willemdebruijn.kernel@gmail.com>,
gnault@redhat.com
Subject: Re: [BUG] Dependence of routing cache entries on the ignore-df flag
Date: Wed, 3 May 2023 11:35:28 -0700 [thread overview]
Message-ID: <20230503113528.315485f1@hermes.local> (raw)
In-Reply-To: <CAJGXZLjLXrUzz4S9C7SqeyszMMyjR6RRu52y1fyh_d6gRqFHdA@mail.gmail.com>
On Wed, 3 May 2023 18:01:03 +0300
Aleksey Shumnik <ashumnik9@gmail.com> wrote:
> Might you answer the questions:
> 1. How the ignore-df flag and adding entries to the routing cache is
> connected? In which kernel files may I look to find this connection?
> 2. Is this behavior wrong?
> 3. Is there any way to completely disable the use of the routing
> cache? (as far as I understand, it used to be possible to set the
> rhash_entries parameter to 0, but now there is no such parameter)
> 4. Why is an entry added to the routing cache if a suitable entry was
> eventually found in the arp table (it is added directly, without being
> temporarily added to the routing table)?
What kernel version. The route cache has been completely removed from
the kernel for a long time.
next prev parent reply other threads:[~2023-05-03 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 15:01 [BUG] Dependence of routing cache entries on the ignore-df flag Aleksey Shumnik
2023-05-03 18:35 ` Stephen Hemminger [this message]
2023-05-03 23:39 ` Aleksey Shumnik
2023-05-05 3:10 ` David Ahern
2023-05-05 15:00 ` Stephen Hemminger
2023-05-05 15:22 ` David Ahern
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=20230503113528.315485f1@hermes.local \
--to=stephen@networkplumber.org \
--cc=ashumnik9@gmail.com \
--cc=gnault@redhat.com \
--cc=gw4pts@gw4pts.ampr.org \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=waltje@uwalt.nl.mugnet.org \
--cc=willemdebruijn.kernel@gmail.com \
/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.