| Age | Commit message (Collapse) | Author |
|---|
|
of. currently limited to MCLBYTES (2048 bytes) and 4096 bytes until pools
can allocate objects of sizes greater than PAGESIZE.
this allows drivers to ask for "jumbo" packets to fill rx rings with.
the second half of this change is per interface mbuf cluster allocator
statistics. drivers can use the new interface (MCLGETI), which will use
these stats to selectively fail allocations based on demand for mbufs. if
the driver isnt rapidly consuming rx mbufs, we dont allow it to allocate
many to put on its rx ring.
drivers require modifications to take advantage of both the new allocation
semantic and large clusters.
this was written and developed with deraadt@ over the last two days
ok deraadt@ claudio@
|
|
which are considered down will no be marked ~RTF_UP and so multipath routing
will start to work as expected and not pump 50% of the traffic to nirvana.
Most of the magic happens in rn_mpath_reprio() which fiddles with the
routing table internals. The rest is more straight forward.
get it in deraadt@
|
|
fill a slot when the mbuf allocator gives us an mbuf cluster.
|
|
|
|
|
|
|
|
and detach devices on a gpiobus at runtime. The offset and mask locators
in kernel config files can still be used for static configuration, so this
does not break existing custome kernel configs.
- Have gpioow(4) unmap the pins it used from the gpiobus during detach
Changes to gpioctl(8) will be a separate committ.
ok uwe
|
|
This lets early arc4random() calls to return at least non-uniqe values
on different machines. The dmesg will have different MAC addresses,
etc. Also ignore the entropy count in arc4_stir, and just take what's
there. sizeof(struct timeval) should be sizof(struct timespec)
This was forgotten when we switched to nanotime.
With help from mickey.
OK djm@, deraadt@
|
|
|
|
Someone must have fumbled with this line by accident while doing the
original port of the driver.
|
|
but anyway reset the eof condition on stdin, so you don't get an
infinite loop in the typical program after a ^D.
reported by Tamas TEVESZ.
|
|
|
|
Add SDMMC_ASSERT_LOCKED(), replacing many locking calls, and sprinkling
the assertion to make sure that future changes don't catch us out
"please commit" uwe@
|
|
dma_bufs; allow the driver to provide the size and not have the private
data pointer. only radeon only needs this so far, but intel with GEM
also needs it.
Postclose was only used for freeing said private data, so this allows me
to remove the postclose callback and rename preclose to close.
|
|
ask the driver how large they need the structure we allocate to be, and
use inheritance like we do for struct device. Simplifies things a little
bit and saves us a pointer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
setup the drm_attach_args with the needed information.
require interface version 1.1 libdrm has been requesting it for ages),
which means that we can set the busid string at attach time. (generated in
drm_attach_pci), also pass in the interrupt line and bst.
Now we don't need dev->pa at all, so remove it, finally.
|
|
other way round. More dev->pa reduction
|
|
not zero it during the cleanup ioctl.
|
|
|
|
the ioctl handler.
|
|
leave the rest alone. Also don't read *spte twice and compare results.
feedback drahn@ okay art@ weingart@
|
|
on X startup.
found by ckuethe@
|
|
bits necessary. Also move up the pmap_map_ptes() call to before the
diagnostic check. okay art@, weingart@
|
|
"I'm all for it." marco@ "Yeah" deraadt@
|
|
|
|
|
|
|
|
though if no new features are in play. diff from Wouter Godefroy
|
|
part of a server. there's no configuration yet, and several other drawbacks,
but it can be hammered into shape. i haven't moved the code forward in a year,
and marco wants it in the tree to hack on.
|
|
|
|
|
|
size.
kill (empty) drm_mem_{un,}init() while here.
|
|
While we don't have code for this (yet!), mean I will be able to update
libdrm, and consequently the xf86-video-intel driver to 2.5.x.
Add PARAM_HAS_GEM to the getparam ioctl, and return no support.
|
|
ok yuo@
|
|
dev->pa by doing the pci_intr_establish/disestablish dance in the driver
function, not in drm. This removes the need for
interrupt_{pre,post}install callbacks, instead just provide a
interrupt_install() callback.
|
|
just put a vblank_pipes argument to the driver structure which tells us
how many to set up
this means that intel doesn't lose all vblank count on vtswitch (it
disables the interrupt there), i've heard of a few uvm_faults where this
happens as well as things just going wrong.
This was suggested by Keith Packard who provided a different diff for
drm.git.
|
|
Not enabled in any kernel (and will not be).
ok drahn, uwe
|
|
|
|
|
|
from wiz@netbsd
|
|
|
|
ok dlg
|
|
ok deraadt@ claudio@
|
|
|
