| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
| |
- Keep class-specific data in conf.sh file.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
the keg/zone lists, summarizing cache state, and walking bucket lists in
each zone. I seem to get inconsistent results on SMP, possibly due to
local header problems, but it seems to work quite well on UP. This tool
requires sufficient privilege to read /dev/mem (or a core dump), and is
for debugging purposes rather than administrative monitoring purposes
(use vmstat instead).
|
| |
|
| |
|
|
|
|
|
| |
events are now plotted as a counting graph, similar to CPU load, so that
their duration and critnest values can be visualized.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
o Change the result of gctl(001) now that a bogus verb still requires
a valid geom,
o Insert gctl(024) to test for an appropriate error when a bogus verb
is given that does have a proper geom parameter.
|
|
|
|
|
|
|
|
|
|
|
| |
whole name. This does not unnecessarily close the door that in some
future we want to test on something other than md(4) devices.
Also add a "conf" action so that we can check whether a gctl actually
did the right thing or not. It's one thing to check that the result
strings are as expected, but it doesn't tell us if the end result is
correct. This needs a bit more fleshing out, but for now a visual
(i.e. manual) check suffices.
|
|
|
|
| |
file descriptor passing. These tests are not all currently passed.
|
| |
|
|
|
|
| |
(eg. "ttyv0" and "v0").
|
| |
|
|
|
|
| |
when running on traces referencing >2 CPUs.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
PR: misc/88549
Submitted by: Sokolov Alexey
MFC after: 1 week
|
|
|
|
|
|
|
| |
I'll commit real soon.
Count the number of found test cases instead of hard-coding them. Allow an
arbitrary exit status.
|
|
|
|
|
| |
I changed every u_int64_t to uintmax_t, as we should use eventually
uint64_t anyway those days.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tool:
- Use uname(3) to query the OS name to report in the HTTP headers.
This is probably more useful than hard-coding FreeBSD.
- If no path is specified, create a 1k temporary file and send that
instead. Pass a file descriptor into http_serve() rather than using
a global fd.
- Add more carriage returns to the HTTP headers to be a bit more
correct. (Suggested by: andre)
- Read to a buffer rather than a single character to reduce the number
of recv() system calls pulling in the HTTP request.
- Properly wait for two, not one, \n's on input.
|
|
|
|
| |
probably a bug in the parser.
|
|
|
|
| |
should fail because of a bug in the parser (test 2).
|
| |
|
| |
|
|
|
|
|
| |
in-memory changes only and as such are only useful for prototyping
and regression testing purposes.
|
| |
|
| |
|
|
|
|
| |
of the sendfile() system call.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- http is a lightweight, multithreaded HTTP query tool, which performs
a timed measurement of the rate at which it can download files using
single-fetch HTTP/1.0. Other than specifying the IP and a URL path,
it requires zero configuration.
- httpd is a lightweight, multithreaded HTTP server tool, which exports
a single file of choice to the HTTP client, and responds with it no
matter what the request. Other than specifying the file to export,
it requires zero configuration.
The goal of these tools is to measure the network costs associated with
HTTP serving, rather than file system, HTTP protocol parsing, error
handling, etc, and as such, parts relating to less interesting components
of HTTP testing are intentionally omitted. Both are linked against
libpthread by default.
|
|
|
|
|
| |
measure the rate of TCP connection round trips supported by a host at
the socket layer.
|
| |
|
| |
|
|
|
|
| |
Fix NANO_TOOLS usage in FlashDevice()
|
| |
|
|
|
|
| |
based is far better and the only one supported from now on.
|
| |
|
|
|
|
|
|
|
|
| |
of $NANO_SRC, which can e.g. be used if the nanobsd scripts are not in
the source tree being built.
Improved by: phk
Approved by: phk
|
|
|
|
|
| |
Spotted by: Andrea Campi <andrea+freebsd_cvs_all -at- webcom.it>
Pointy hat to: philip
|
| |
|
|
|
|
|
|
|
|
| |
for commonly used flash devices by
FlashDevice Sandisk 256MB
in the config file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
there for scripts to use.
Create a noauto fstab entry for the configuration partition (/cfg).
Add NANO_TOOLS env-var to point to the nanobsd sources relative to
NANO_SRC.
Add -h argument which prints a usage.
Add -b argument which skips build steps and goes directly to install steps.
Complain about extraneous arguments, it's usually a forgotten '-c'
Add convenience function to register customization function.
Add some sample customization functions:
cust_comconsole
cust_allow_ssh_root
Rename setup_diskless() to setup_nanobsd(), it makes more sense.
Add various comments etc.
|