| Age | Commit message (Collapse) | Author |
|---|
|
file becoming readable increase.
|
|
* altq for loop is just for debugging.
* only used when called for loop interface (not for
* a simplex interface).
*/
bye bye!
|
|
ALTQ has served us well for years and was extremely important not just for
us, but for the entire bandwidth management arena. Back when we got altq,
the subject was not yet well researched and understood, which is why altq
is the framework with pluggable schedulers it is. Kenjiro Cho (kjc@) did an
amazing job there.
Now, more than 10 years later, we do have a good understanding and can use
a simpler framework with just one priority queueing and one bandwidth
shaping mechanism each - the new queueing subsystem. Last not least because
it is incredibly painful to maintain both in parallel, it is time for altq
to depart. Farewell, thanks for many years of good service. Everybody
using any form of "not just fifo" queueing owes Kenjiro a lot. At least
buy him a beer when you meet him.
And, allow me this personal note, thanks Kenjiro, working with you on the
topic has always been a great pleasure and I learned a lot from you. Thanks!
|
|
ok dlg@
|
|
tested by jmatthew@
|
|
|
|
add attributes to it later; as wd33c93 is not a valid device name.
ok miod@
|
|
the process, not just the thread.
ok kettenis@
|
|
Add a check for IPv4-mapped IPv6 destination addresses, like in the most
recent KAME code, for non-connected sockets. This prevents packets from
reaching the wire through the default route, if a reject route
for ::ffff:0.0.0.0/96 isn't present. ok claudio@
|
|
|
|
|
|
manually, ok naddy (in january)
|
|
ok benno lteo naddy (back in january)
|
|
|
|
don't panic, but just return.
tested by nicm@
ok tedu@
|
|
to avoid possible use-after-free references when swapping ids in threaded
processes. "Do I have the right creds?" checks are always made with the
threads creds.
Inspired by FreeBSD and NetBSD
"right time" deraadt@
|
|
error code and pass the resulting source address back to the caller
through a pointer, as suggested by chrisz. This gives us more readable
code, and eases the deletion of useless checks in the callers' error path.
Add a bunch of "0 -> NULL" conversions, while here.
ok chrisz@ mpi@
|
|
This will give us basic support there are a few extra bits in the linux
driver we ignore for now. Something to look at in the future.
OK stsp@ mlarkin@ kettenis@
|
|
comes back, so later on we can work out what to do when logins fail
|
|
interrupt, as done in qla(4).
|
|
reliably tell when we've been through the whole list.
|
|
Simplifies things a bit and makes pre- and post- attach operations work
the same.
|
|
completely detached from the process before letting it exit, so that
sleeping in systrace_exit() doesn't reorder them and lead to a panic.
Panic reported by Fabian Raetz (fabian.raetz (at) gmail.com)
ok tedu@
|
|
Fix some parameters and wording too.
|
|
it rather than on attach. just need to implement a sense handler
to detect failover and this is done.
thanks to jmatthew@ for plugging this together again for me.
|
|
was done by Pedro Martelletto for bitrig. One small tweak to make it buildable with -Werror. "Please commit" miod@
|
|
IP_SENDSRCADDR support. This reduces the differences with the
IPv6 version and kill some comments that are no longer true.
ok jca@, chrisz@, mikeb@
|
|
LUNA-88K.
LUNA-88K{,2} has one or two slot(s) that can attach the extension
board designed for PC-9801. This driver provides dedicated mmap(2)
and capability for waiting specified interrupt on that slot so that we
can use the extension board from userland program.
(*)PC-9801 is a Japanese popular personal computer, mainly used in
1980-90's. (see http://en.wikipedia.org/wiki/NEC_PC-9801)
ok miod@, and man pages jmc@
|
|
|
|
nvme and other stuff.
|
|
entry. if i ever implement timeouts ill use high bits in the int
or the phase bit to indicate non chip related errors. a successful
chip status conveniently maps to 0. how handy.
this lets me move the completion handling for the controller
identification commands back into the caller. at the moment im just
printing out controller and firmware details like we do on
mfi/mpii/mfii.
|
|
steps, but unfortunately the next step after "talk to the chips
registers" was "get command queues working" which ended up being a
huge amount of plumbing.
anyway, this lets me successfully run an identify controller command
against the chip and should be cut up the right way to be usable
for io command submissions. will need to think about how to avoid
overflowing rings though.
|
|
instead of using the default, per-driver, one. This is a step to move
away from the 1 report ID <-> 1 driver design which is no longer true
since the addition of upd(4).
ok andre@
|
|
noticed by pedro@ in bitrig.
ok philip@ millert@
|
|
Avoid the confusion by using an appropriate name for the variable.
Note that since routing domain IDs are a subset of the set of routing
table IDs, the following idiom is correct:
rtableid = rdomain
But to get the routing domain ID corresponding to a given routing table
ID, you must call rtable_l2(9).
claudio@ likes it, ok mikeb@
|
|
|
|
|
|
post-attach mailbox operations work reliably.
|
|
emphatic ok usual suspects, grudging ok miod
|
|
|
|
to sleep, instead of just the acpi thread going to sleep.
|
|
Fix some parameters and wording too.
|
|
ok miod@
|
|
time also. Let's commit this idea since it is sound, and keep an eye
for reports.
discussed months ago with kettenis and mlarkin
|
|
(race condition ?)
problem noticed by me, aja, sthen, brynet, rpe.
vanishing after this revert, okay aja@, sthen@
tedu, you probably want to look into re-checking the fcreate/fpublish addition
first, then if it's stable, see about tweaking doopenat ?
|
|
|
|
|
|
From Rob Clark
8af4707afcb6d191b9cc75dfd73b9550e8276253 in ubuntu 3.8
9ef7506f7eff3fc42724269f62e30164c141661f in mainline linux
|
|
From Alex Deucher
20b03e738e7ded3ab66dd7dd3c3ac198c8531381 in ubuntu 3.8
d03874c881a049a50e12f285077ab1f9fc2686e1 in mainline linux
|
|
From Lauri Kasanen
7e88b3ea565f869721b8ac011ee73b95b773e938 in ubuntu 3.8
14eedc32a3c0ec9dd70448a73763ee21feae3111 in mainline linux
|
