Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 May 2021 21:34:03 +0200
From:      Hans Petter Selasky <hps@selasky.org>
To:        Ryan Stone <rysto32@gmail.com>, freebsd-net <freebsd-net@freebsd.org>
Subject:   Re: rip6_output not in net epoch across call to ip6_setpktopts()
Message-ID:  <f7234a05-c892-ea68-105f-78c6e1094650@selasky.org>
In-Reply-To: <CAFMmRNziwec6GeuDvvhXzQE=z5boxXqT0pwDUu628dcYQWiKbQ@mail.gmail.com>
References:  <CAFMmRNziwec6GeuDvvhXzQE=z5boxXqT0pwDUu628dcYQWiKbQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 5/18/21 9:18 PM, Ryan Stone wrote:
> The issue seems to be that rip6_output() calls into ip6_setpktopts()
> outside of the net epoch.  Should I just wrap the setpktopts call in a
> net epoch enter/exit, or does anybody think that there's something
> cleverer that should be done there?

Hi,

Epoch automagically detects recursion, and optimizes for that. If there 
is an inner section of enter/exit, covered by an outer section, the 
overhead will be less for the inner section.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f7234a05-c892-ea68-105f-78c6e1094650>