Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Oct 2016 15:05:10 -0400
From:      Jonathan Looney <jonlooney@gmail.com>
To:        freebsd-transport@freebsd.org
Subject:   Remove (struct tcpcb) from the API?
Message-ID:  <CADrOrmuG_GvqnenU8g9UXGN3uPDyMOapHm%2BX85iNa-RNHp1wUQ@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
Folks,

Currently, the (struct tcpcb) is part of the kernel API. This means that we
can only mess with the "spare" fields when we MFC things.

Currently, things in userland *should* only be using the
'net.inet.tcp.pcblist' to extract the (stuct tcpcb) list from the kernel.
We *should* be able to switch that sysctl so it only copies out the portion
of the (struct tcpcb) that is actually needed by userspace. The trick is
coming up with that list of fields, and then dealing with the fallout when
userspace things not from the base package break.

Does anyone have an idea of whether things in the ports tree use this and
will break? And, does anyone have strong feelings one way or the other?

Jonathan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADrOrmuG_GvqnenU8g9UXGN3uPDyMOapHm%2BX85iNa-RNHp1wUQ>