interface: POC for multi-dhcp6c support
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
At the moment this splits off dhcp6c only but we need to
change the daemon's print a bit to avoid complaining about
"other" devices since the situation to ignore a non-listening
interface is normal and not "ignoring" something obvious as
the INFO log message suggests.
rtsold still needs to be split to allow for HUP reload of
a single interface instead of forcing a restart of all
DHCPv6 WAN clients at the same time.
interface: POC for multi-dhcp6c support
I'm not entirely sure why we settled for a single deamon of
dhcp6c back in the day, but there are certianly downsides to
it and I don't see something that wasn't fixed in the meantime
that makes this not work.
At the moment this splits off dhcp6c only but we need to
change the daemon's print a bit to avoid complaining about
"other" devices since the situation to ignore a non-listening
interface is normal and not "ignoring" something obvious as
the INFO log message suggests.
rtsold still needs to be split to allow for HUP reload of
a single interface instead of forcing a restart of all
DHCPv6 WAN clients at the same time.
For better debugging support in the future ditch the "normal"
log mode and always use -d or -D when debug is wanted.
interfaces: more prepping for multi-dhcp6c
Clear out compatible changes from the branch to make it
lighter. Refactor the command generation to work with
a specific pid and conf per device, but keep the old files
for now.
[mlir][Linalg] Drop unit extent dim in non-trivial expressions (#173873)
The current implementation does not drop unit extent dimension if that
dimension is indexed by a non-trivial affine expression (i.e., not a
single dimension or constant 0) on the first application of the
transformation. However, it is possible to drop such dimensions if all
dimensions involved in the affine expression are going to be dropped. So
far, this required repeated application of the transformation, with the
changes in this PR, the dimensions are dropped with a single application
of the transformation.
Signed-off-by: Lukas Sommer <lukas.sommer at amd.com>
NAS-139051 / 26.04 / Use annotations for public API methods (#17882)
`@api_method` decorator now accepts `check_annotations=True` for this
new behavior. The default is `False`, but we should eventually come to a
state where the default is `True` and this parameter will be remove
altogether.
What changes? First, each public method type annotation will be checked
to match the method's declared accept and return models.
Second: no more dict typing. If the API method accepts a pydantic model,
that pydantic model will be passed to it, not dict. This allows for IDE
autocompletion, static analysis, less AI coding agent errors.
As an example, I converted webshare plugin to this new behavior.
tools/cam: Start to add the testing tools for CAM
Create a directory for testing tools arond CAM. These are snippets of
what will eventually be camio. At the moment, it was written using fbt
traces. This is OK, but fragile, so they need to be re-written with the
cam provider. cam_all_but_scsi.d is the first step. It shows how to do
this with the new cam dtrace provider.
Sponsored by: Netflix
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D54472
tools/cam: Start to add the testing tools for CAM
Create a directory for testing tools arond CAM. These are snippets of
what will eventually be camio. At the moment, it was written using fbt
traces. This is OK, but fragile, so they need to be re-written with the
cam provider. cam_all_but_scsi.d is the first step. It shows how to do
this with the new cam dtrace provider.
Sponsored by: Netflix
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D54472
cam: When inq data isn't valid, pass NULL
When the device isn't there, we don't have valid inq data. Pass NULL in
this case. All the routines that receive this test against NULL already.
Sponsored by: Netflix
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D54470
cam: When inq data isn't valid, pass NULL
When the device isn't there, we don't have valid inq data. Pass NULL in
this case. All the routines that receive this test against NULL already.
Sponsored by: Netflix
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D54470
cam: Start adding dtrace provider 'cam'
Start to provide robust tracing in cam now that clang has broken my
fbt-based dtrace scripts a couple of times.
Sponsored by: Netflix
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D54468
cam: Start adding dtrace provider 'cam'
Start to provide robust tracing in cam now that clang has broken my
fbt-based dtrace scripts a couple of times.
Sponsored by: Netflix
Reviewed by: adrian
Differential Revision: https://reviews.freebsd.org/D54468
