| Age | Commit message (Collapse) | Author |
|---|
|
Precursor to removing rule.action from skip steps.
Also a couple of other small fixes:
- s/PF_RULESET_RULE/PF_RULESET_FILTER/
- replacement of 4 with PF_RULESET_MAX in pfvar.h struct ruleset {
- error handling in ioctl of an invalid value in rule.action
- counting evaluations and matching packets for scrub rules
ok henning@ dhartmei@
|
|
well as the few userland tools which were only used on these platforms.
|
|
There has not been enough activity and interest towards these platform
to keep them lying in the tree.
|
|
ok fgs@
|
|
|
|
|
|
normal configurations, and sufficient for many. You can always increase
it, if you need more concurrent states and have enough memory (65000 for
64MB RAM, for instance). Suggested earlier by henning@. ok mcbride@
|
|
Use increased retries number and don't ignore SCSI_IGNORE_NOT_READY
when call scsi_test_unit_ready() for cd-rom, this makes system wait
if drive is loading media.
Tested by millert@ and fgsch@; some input and ok from krw@.
Problem reported by The lord of the CD-writers
Igor Grabin <violent@death.kiev.ua>.
|
|
PZERO - 4 == 18 which makes it equivalent to PRIBIO; not what we want.
Discussed with art@ some time ago.
|
|
but then check to see that one with our struct proc was not allocated
in the meantime.
|
|
|
|
|
|
Thanks to Clarie Wouter (rimshot at pandora point be)
|
|
|
|
Re-work the SBP2 data manipulation to support concurrent node accesses.
(That data manipulation MUST go into SBP2 code, eventually)
|
|
node_id changes, following a BusReset (happens when you add/remove a device
to/from the FireWire chain).
Re-work the ORB management to support concurrent node accesses.
|
|
65535 bytes blocks silently broke. So limit ourself to 32k blocks, for now.
That mistake gave us the false impression that huge transfers were fast.
They usually resulted of 0-byte transfers. Fast indeed :-(
Now, we have real data going through.
|
|
So just ignore, and continue the auto-configuration.
|
|
|
|
That new key will be used for Request handlers to discriminate the requests
by nodes. Key3 will also get the lenght field specifier... (may still change)
Add an implementation for a BusReset callback that will be called whenever
a node's node_id changes.
This will allow us to work with more than one device at the same time...
|
|
|
|
|
|
|
|
one where semtot was not getting incremented.
|
|
ok dhartmei@, mcbride@, henning@
|
|
|
|
Found by Andrew Pinski <pinskia@physics.uc.edu>
Works with gcc-current and Tendra C++ now.
|
|
- set rpool.cur in DIOCCHANGERULE
- check to make sure rpool.list is not empty if we're doing translation
or routing other than fastroute
ok dhartmei@ henning@
|
|
- pull the route-to ifp from the current pf_pooladdr (not the last one)
with stateful rules
- remove unnecessary PF_ACPY and PF_AZERO
ok dhartme@ on pf_route version, pf_route6 is the same.
|
|
and don't ttymalloc lines we don't have. CXA16 in DHV-11 mode is
probably still not correct.
|
|
redirection target address. Reported by Michael Lucas. ok mcbride@
|
|
Solves the crashes in pf_route() with -current.
Reports from Michael Lucas and Bjorn Runaker.
|
|
|
|
panics should occur. ok mcbride@
|
|
set from <sys.mk>
|
|
|
|
|
|
|
|
from incorrect values, and restore it after X11 use (from macppc).
|
|
|
|
It works even, so enable the dhu.
|
|
|
|
|
|
back in tcpdump, worked fine (; from bdd@ieee.org
|
|
we don't need the second list of addresses for DIOCCHANGE* operations)
Also get rid of a bug where DIOCBEGINADDRS clears pabuf[1] when pabuf[0]
is the one being used.
ok henning@ dhartmei@
|
|
|
|
from dev/ic/wdc.c; from NetBSD.
ok miod@ deraadt@
|
|
Assign a fixed value (SIOP_NTAGS) to the openings field in the
adapter's template sc_link, rather than incrementing the value as
cbd's are allocated. The template value is the one copied into each
device's sc_link structure as it is created.
Incrementing the value meant that each new device got a larger value
for openings. The total number of openings claimed by devices on a
bus soon exceeded the number of cbd's available. e.g. after 5
devices there would be 132 allocated cbd's, but the total number of
openings claimed by devices would be 300.
A heavy i/o load on an adapter with multiple devices could have
caused the upper scsi layer to try to queue more i/o's than the
driver had cbd's to store them in. Such i/o's would fail with EIO if
they were started with SCSI_NOSLEEP (e.g. sdstart()) or were not
queued within the specified retry limit. I/o's for devices 'later'
on the bus would be more likely to trigger this behaviour, due to
their inflated openings values.
This is good candidate for -stable.
|
|
referenced by number in DIOCCHANGEALTQ (like rule and pooladdress)
"go for it" henning@
|
|
ok costa@
|
