| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
all requests from the queue if request number is not given.
Bump version number.
Approved by: re (scottl)
|
| |
|
|
|
|
| |
mutex to be held here, because we want speed here.
|
|
|
|
|
|
|
| |
This flag means "wait for all pending requests before returning to userland".
There are pending events for sure, because we just created new provider and
other classes want to taste it, but we cannot answer on I/O requests until
we're here.
|
|
|
|
|
| |
Submitted by: Andreas Kohn <andreas.kohn@gmail.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
4 mutex operations per I/O requests.
- Use only one mutex to protect both (incoming and outgoing) queue.
As MUTEX_PROFILING(9) shows, there is no big contention for this lock.
- Protect sc_queue_count with queue mutex, instead of doing atomic
operations on it.
- Remove DROP_GIANT()/PICKUP_GIANT() - ggate is marked as MPSAFE and no
Giant there.
|
|
|
|
|
|
| |
- Improve mediasize checking.
MFC after: 1 week
|
|
|
|
| |
- Move DROP_GIANT()/PICKUP_GIANT() to g_gate_ioctl().
|
|
|
|
|
|
|
| |
MT5 candidate.
PR: kern/72253
Submitted by: Ivan Voras <ivoras@fer.hr>
|
| |
|
|
|
|
|
|
|
|
| |
for unknown events.
A number of modules return EINVAL in this instance, and I have left
those alone for now and instead taught MOD_QUIESCE to accept this
as "didn't do anything".
|
| |
|
|
|
|
|
|
|
|
| |
Now, when trying to mount file system in read-only mode it tries to
opened a device for writting to be able to update to read-write mode
latter. Ehh.
Discussed with: phk
|
|
|
|
| |
Found by: KASSERT()
|
|
|
|
| |
Bump __FreeBSD_version accordingly.
|
| |
|
| |
|
|
|
|
|
|
| |
Found by: mtx_assert() g_gate.c:273
- Set command before returning to userland with ENOMEM error value.
Found by: assert() ggatel.c:108
|
|
|
|
|
| |
The biggest issue was that 16-bit atomic operations aren't supported
on all architectures.
|
|
|