Age | Commit message (Collapse) | Author |
|
it up in pf_setup_pdesc(). ok ryan benno mikeb bluhm
|
|
instruction, before testing whether it can be built with `or.u'; this
allows further optimization.
condition_value(): handle ORDERED and UNORDERED condition codes.
print_operand(): remove support for no longer used `w' qualifier.
|
|
just return after being done with the address. ok bluhm ryan mikeb
|
|
inline assembly, tb/tbnd instructions.
Don't use `r' qualifier for "register_operand", it's redundant.
|
|
others); concept and keymap table (covering about 400 layouts) from
modhex.js by Daniel Holth.
ok sthen@, ok halex@ (who also provided much testing and feedback)
|
|
because that resulted in corrupt output.
This is a verbatim backport of the following bugfix from upstream git master:
https://rt.cpan.org/Public/Bug/Display.html?id=77465
https://github.com/mrallen1/Pod-Perldoc/commit/6e1541d0bcb74a7b2b9ee3235d57953fb800bb67
Do not take the comment in the source code too literally.
It doesn't really explain the problem well.
OK sthen@ espie@ millert@
|
|
|
|
just hard code 4096 for now instead of anything fancy.
|
|
|
|
|
|
|
|
|
|
removed at n2k13 but a few errant references still remained. No functional
change. Spot tested by my on i386 and amd64 UP environments, no regressions
seen.
noticed by deraadt@
|
|
|
|
|
|
|
|
This adds information about smt id (thread), core id and package id
(socket) to amd64.
ci_smt_id, ci_core_id, ci_pkg_id should be followed by other
archictectures and core relying on them should be under
ARCH_HAVE_CPU_TOPOLOGY.
ok tedu@
|
|
|
|
Problem noted, fix tested and ok sthen@.
|
|
|
|
David Imhoff. No functional change.
|
|
DCTL flag defines. Now with the right defines, doh!
|
|
DCTL flag defines. No binary change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
build.
|
|
privileged operations for raw sockets and bind any.
|
|
feature. It requires two machines, the local host is running the
regression test, the remote host gets pf divert rules installed.
The diverted TCP connections are running between these hosts in
both directions. The remote host is controlled via ssh.
|
|
ok guenther
|
|
- Remove _PC_PATH_MAX, _PC_PIPE_BUF and _PC_SYNC_IO.
- Add _PC_TIMESTAMP_RESOLUTION.
- Change _PC_FILESIZEBITS from using "sizeof(off_t) * CHAR_BIT" to returning 64.
With input from and Ok guenther@
|
|
Diff by Renato Westphal
|
|
* Send an extra Hello message before attempting to connect to a remote
peer to guarantee that it formed an adjacency with us as well;
* Don't wait for the first timeout to send the first Hello message.
Both tricks together will allow for fast session establish since with both
optimizations passive role neighbors can open the connection immediatly by
sending and receiving the hellos at the same time as the TCP session.
From Renato Westphal
|
|
it belongs only _after_ receiving an Initialization message containing
the information we need. Before an Initialization message is received,
the TCP connection shouldn't be associated with any neighbor/adjacency.
Therefor refactor that part into a own module.
From Renato Westphal
|
|
|
|
ok deraadt@, miod@
|
|
for inteldrm(4).
ok miod@, kettenis@
|
|
|
|
From Renato Westphal
|
|
From Renato Westphal
|
|
|
|
Refactor adjacencies out of the neighbor handling so that it is possible to
have more complex topologies with targeted sessions.
From Renato Westphal
|
|
macros that are mandated by POSIX
ok matthew@ tedu@
|
|
|
|
clean some related code.
|
|
|
|
According with the section 2.5.3 of RFC 5036, an LSR must throttle its
session setup retry attempts with an exponential backoff in situations
where Initialization messages are being NAK'd (because of disagreements
on session parameters). It doesn't mention using this procedure for TCP
connection failures. With that said, start the inactive delay timer only
after receiving an appropriate notification message.
When playing the active role of the initialization process, throttle the
session setup retry attempts by not connecting to the remote peer. When
playing the passive role, throttle the session setup retry attempts by
delaying the processing of the received Initialization message.
Diff by Renato Westphal, adjusted by myself
|