| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
remove the code from libkvm that dealt with it.
|
|
|
|
In snaps for a while.
|
|
Another evil jumbo allocator bites the dust.
|
|
|
|
when recording
ok oga, deraadt
|
|
In the future, we need to mark the correct parts of the direct map
uncached, but that's another diff.
art@, kettenis@ ok.
|
|
ok art@, henning@
|
|
Prodded by & ok jmc@
|
|
Prodded by & ok jmc@
|
|
|
|
|
|
|
|
|
|
get really fast; ok canacar
|
|
- clarify the terms geometry sectors field and start field
- change the fdisk prompt from 0 to 1, and explain its meaning
- temper CAVEATS: the note is "common practice", not mandatory
from nick and myself
|
|
|
|
this conversion is the easiest ive done so far. the mbuf allocation wrapper
in the driver already had code to handle a failing cluster allocator as
part of a test harness, now we test that code all the time with MCLGETI.
ok kettenis@
tested by phessler@
|
|
if you disable the device.
noticed by deraadt@.
|
|
|
|
|
|
|
|
|
|
add two more {GET,SET}_PARAM arguments that aren't supported yet but are
needed for a libdrm update.
|
|
|
|
ok deraadt@, miod@
|
|
Serial Technologies Expander PCI-232-108
|
|
|
|
between instances, saving space in the kernel. feedback from many (some
incorporated, some left for future work).
ok deraadt, kettenis, "why not" miod.
|
|
allocates clusters larger than 2k.
ok deraadt@
|
|
This implements the first stage of the shortest path tree calculation
(Dijkstra calculation) as outlined in rfc5340, with the exception that
we do not yet treat multiple router LSAs originated by a single router
as an agregate. For now, we only use the Router LSA with the lowest link
state ID.
For each destination, show the calculated set of nexthops in the debug log.
We can stop doing this once spf tree calculation has been shown to be stable.
"A lot of debug code but yes why not. commit it." claudio@
|
|
last commit. Next hop IP addresses and outgoing interfaces can now
be correctly determined, paving the way for SPF tree calculation.
Arguments have changed, so update callers, too.
ok claudio@
|
|
next-hop calculation.
In OSPFv3, next-hop IP addresses are always link-local.
The kernel will want to know which interface the link-local
address belongs to, so we need an ifindex in struct v_nexthop
in addition to the IP address.
Because we cannot determine a link-local next hop IP address
for transit networks, only the outgoing interface will be recorded.
Update calc_nexthop_add() according to the above.
Also add new helpers calc_nexthop_lladdr() and calc_nexthop_transit_nbr(),
to figure out link-local addresses of nexthop neighbours.
ok claudio@
|
|
ok krw@
|
|
A router vertex w has a point-to-point link back to a router
vertex v if v's router ID occurs as neighbour ID in one of the
point-to-point links described in w's router LSA.
A router vertex w has a link back to a network vertex v if the router
ID of v's advertising router (i.e. DR) occurs as neighbour ID in one
of the transit links described in w's router LSA, and v's interface
ID to the network matches the neighbour interface ID of that transit
link.
A network vertex w has a link back to a router vertex v if v's router
ID occurs in the list of attached routers in w's network LSA.
Also, get_rtr_link() and get_net_link() take an unsigned int now.
"commit it" claudio@
|
|
use less local variables. Makes it consistent with get_rtr_link().
ok claudio@
|
|
it was always returning the first link in the LSA, no matter
which link was requested. Fix this bug. Also, decrease the
number of local variables while here, and convert the idx argument
to unsigned int. Adjust one caller to pass an unsigned int,
other callers will be handled in follow-up commits.
ok claudio@
|
|
pointed out by and ok claudio@
|
|
spotted by Jonathan Armani <dbd@asystant.net>
|
|
LSAs originated by the same router the one with the lowest link
state ID.
ok claudio@
|
|
are subtracted from the total length.
ok claudio@
|
|
Most obvious use is to log router IDs.
To facilitate logging of multiple IDs within the same format string,
we use NUM_LOGS static buffers, just like log_sockaddr() does.
help and ok claudio@
|
|
can make use of it much better. No functional change.
ok claudio@
|
|
In Network-LSAs, the only thing sitting between the LSA header
and the attached router list is the options field. We already
have lsa_net_link to represent elements of the attached router list,
so there's no need to have a single entry of this list in lsa_net.
ok claudio@
|
|
Make this a more general concern about using 0 as key id. After discussion with
Tamas TEVESZ
|
|
Calculate offsets with a struct lsa_net_link pointer instead.
ok claudio@
|
|
always retrieve the font metrics, even on older (< 2.9) prom, so do it.
|
|
Help from kettenis@
|
