| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: pluknet
|
|
|
|
| |
Reported by: pluknet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It seems axe(4) controllers support interrupt endpoint such that
enabling interrupt endpoint generates about 1000 interrupts/sec.
Controllers transfer 8 bytes data through interrupt endpoint and
the data include link UP/DOWN state as well as some PHY related
information. Previously axe(4) didn't use the transferred data and
didn't even try to read the data. Because axe(4) counts on mii(4)
to detect link state changes there is no need to use interrupt
endpoint here.
This change fixes generation of unnecessary interrupts which was
seen when interface is brought to UP.
No objections from: hselasky
|
|
|
|
|
|
|
| |
still allows us to build tblgen and clang, and further reduces the
footprint in the tree.
Approved by: rpaulo (mentor)
|
|
|
|
|
|
|
|
| |
make it like xArg because they are different ('x' doesn't accept sign,
but 'r' does).
This fixes some warnings when building DDB with clang.
With help from: rdivacky
|
|
|
|
|
|
|
| |
the system as well has how many PMCs there are per CPU. In this code
CPU and core are equivalent.
MFC after: 1 day
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove or re-work support for the several features from the past:
- remove incomplete support for trimming slice/partition names
- remove mapping from old device names "sd" and "st"
- remove whitespace trimming
- remove unconditional skipping of leading 'r' in a device name
- skip leading 'n' or 'e' only if the following device name matches
a list of known devices that support no-rewind and eject-on-close
features; currently this is only sa(4)
- reflect the above changes in comments in code and in cam(3)
- remove a note cautioning against use of cam_get_device and
cam_open_device in cam(3)
Reviewed by: mjacob
|
|
|
|
|
| |
added on r208987.
These are undocumented but are part of printf(9).
|
|
|
|
|
|
|
|
|
| |
in mfireg.h.
Submitted by: gcooper
Reviewed by: jhb
Approved by: cperciva (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
VFS to OpenSolaris-specific ioflag expected by ZFS. Use it for read and write
operations.
Reviewed by: mm
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
invoke the utilities can robustly report errors.
Submitted by: gcooper
Reviewed by: jhb
Approved by: cperciva (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
| |
- Ensure that the error message is NUL-terminated before printing it.
PR: bin/147482
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
breakage for old mount(2) syscall, since most struct <filesystem>_args
embed export_args. The mount(2) is supposed to provide ABI
compatibility for pre-nmount mount(8) binaries, so restore ABI to
pre-r184588.
Requested and reviewed by: bde
MFC after: 2 weeks
|
|
|
|
|
|
| |
Suggested by: kib
Approved by: kib (mentor)
MFC after: 5 days
|
| |
|
|
|
|
|
|
| |
Suggested by: alc
Reviewed by: alc
MFC after: 1 week
|
|
|
|
| |
PR: 150921
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is to prevent caching of its value in a register when it is checked
and modified by multiple CPUs in parallel.
Also, move the variable into the scope of the only function that uses it.
Reviewed by: jhb
Hint from: mdf
MFC after: 1 week
|
|
|
|
|
| |
PR: 150862
Submitted by: Kris Moore
|
|
|
|
|
|
|
|
| |
cope. Skip multiple spaces in a few contexts.
PR: 96854
Submitted by: Shin'ya Kumabuchi
MFC after: 1 week
|
|
|
|
|
| |
Submitted by: b. f.
Approved by: wes (mentor implicit)
|
|
|
|
| |
Approved by: wes (mentor implicit)
|
|
|
|
|
|
|
|
|
| |
When set, it forces all timestamps and owners to zero and
modes to 0644. Useful for producing libraries that are
bitwise identical across multiple build runs.
Submitted by: Erik Cederstrand
Reviewed by: Kai Wang
|
|
|
|
|
|
|
|
|
|
| |
rwlock to protect the table. In old code, thread lookup is done with
process lock held, to find a thread, kernel has to iterate through
process and thread list, this is quite inefficient.
With this change, test shows in extreme case performance is
dramatically improved.
Earlier patch was reviewed by: jhb, julian
|
|
|
|
|
|
|
|
|
| |
This corrects writing to append-only files on ZFS.
PR: kern/149495 [1], kern/151082 [2]
Submitted by: Daniel Zhelev <daniel@zhelev.biz> [1], Michael Naef <cal@linu.gs> [2]
Approved by: delphij (mentor)
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
Found by: clang
Submitted by: Norberto Lopes, nlopes dot ml at gmail dot com
Approved by: rpaulo (mentor)
|
|
|
|
|
| |
case of a multi-interfaced host, sub-second flapping can fill up the logs
too quickly. This fixes that.
|
| |
|
|
|
|
|
|
| |
driver is not running there is no need to up the interface. While
I'm here hold driver lock before modifying MTU as it is referenced
in RX handler.
|
|
|
|
|
| |
Mailwrapper can provide a perfectly good rmail with other
mailers.
|
|
|
|
| |
Suggested by: pjd, ivoras, arundel
|
|
|
|
|
|
|
| |
once during start-up.
Reported by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
error messages, so when we clean up after child process, we have to check if
the event socketpair is still there.
Submitted by: Mikolaj Golub <to.my.trociny@gmail.com>
MFC after: 3 days
|
|
|
|
|
|
| |
to the expected type so they work like the corresponding __bswapN_var()
functions and the compiler doesn't complain when arguments of different
width are passed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- tcpconnect incorrectly uses err() in usage() with errx() semantics [1]
That produces dirty error message:
tcpconnect: usage: tcpconnect [ip]: Unknown error: 0
- 64-bit aware fixes in printf() usage [2]
o netrate/juggle: time_t has arch-dependent size
o netrate/tcpconnect: don't assume %ll has always 64bit.
PR: 146088 [1], 146086 [2] (modified)
Approved by: kib (mentor)
MFC after: 1 week
|
|
|
|
| |
They have no effect when coming in pairs, or before .Bl/.Bd
|
| |
|
|
|
|
|
|
| |
/usr/include.
Discussed with: kib
|
|
|
|
|
| |
PR: bin/145921
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
Submitted by: arundel
MFC after: 3 days
|
|
|
|
|
| |
Requested by: danfe
MFC after: 6 days
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
opposition to the change, since really we need to implement missing
functionality in drivers or the 802.3 layer.
For now, restore a reminder message for a missing rum_update_mcast, but
print it only once.
|
|
|
|
|
|
|
|
| |
process address.
Add "tdaddr" keyword to ps(1) to display this thread address.
Distilled from Sandvine's patch set by Mark Johnston.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
controller, but make it optional.
After a problem report from Andrew Boyer, it looks like the LSI
chip may have issues (the watchdog timer fired) if too many aborts
are sent down to the chip at the same time. We know that task
management commands are serialized, and although the manual doesn't
say it, it may be a good idea to just send one at a time.
But, since I'm not certain that this is necessary, add a tunable
and sysctl variable (hw.mps.%d.allow_multiple_tm_cmds) to control
the driver's behavior.
mps.c: Add support for the sysctl and tunable, and add a
comment about the possible return values to
mps_map_command().
mps_sas.c: Run all task management commands through two new
routines, mpssas_issue_tm_request() and
mpssas_complete_tm_request().
This allows us to optionally serialize task
management commands. Also, change things so that
the response to a task management command always
comes back through the callback. (Before it could
come via the callback or the return value.)
mpsvar.h: Add softc variables for the list of active task
management commands, the number of active commands,
and whether we should allow multiple active task
management commands. Add an active command flag.
mps.4: Describe the new sysctl/loader tunable variable.
Sponsored by: Spectra Logic Corporation
|