Age | Commit message (Collapse) | Author |
|
|
|
|
|
After configuring a watch for the node, XenStore will asynchronously
notify the system when the value of the specified node changes with
an event message.
|
|
the generation bit to pass the tx descriptor and mbuf to the "hardware".
This way bpf is not called if vmxnet3_load_mbuf dropped the mbuf.
Tested by me
OK mikeb@
|
|
from richard proctor on bugs@
|
|
diff from richard proctor on bugs@
|
|
drivers update hardware configuration accordingly.
tested by myself, tb@, deraadt@, abieber@
ok mpi@
|
|
the hardware. This could have resulted in a page fault when the mbuf
has already been freed by the TX interrupt handler on another CPU.
This has the slight drawback that bpf can be called before the packet
is eventually dropped by vmxnet3_load_mbuf() - but I'm getting this
simple and verified fix in before doing further optimizations on the
start handler.
As discussed with mikeb@ jsg@ dlg@
|
|
|
|
|
|
|
|
Xen doesn't provide a way for a guest to decide which model of
the interface is selected in the VM configuration and therefore
there's no simple way for Netfront and emulated devices to co-
exist on the same system. Emulated em(4) or re(4) drivers will
take over if xnf(4) driver is disabled or not compiled in.
Idea and OK reyk
|
|
ahci_pci updated to cope with the new pcidevs id for its sm951
|
|
|
|
ok ratchov@ deraadt@
|
|
another bug introduced in my turbo mode removal commit; Now fixed.
Keep the debug printf added in r1.155.
|
|
Seems to make Tx rate scaling go up faster and helps Rx performance.
ok deraadt@
|
|
For some reason we would end up passing channel number zero to
the RXON firmware command, which the firmware doesn't like.
ok sthen@ reyk@
and also tested by stefan@, deraadt@, mikeb@
|
|
|
|
now that start and txeof can run on different cpus, txeof could
have freed the mbuf before bpf got to it.
|
|
noone could understand how em_txeof worked, so i rewrote it.
this also gets rid of the sc_tx_desc_free var that needed atomic
ops. space to use in em_start and space to free in em_txeof is now
calculated from the producer and consumer.
testers have reported better responsiveness with this. somehow.
if em issues persist after this, im rolling back to pre-mpsafe changes.
|
|
|
|
|
|
|
|
From Nathanael Rensen, ok dlg@
|
|
ok deraadt@
|
|
|
|
shorten a bunch of variable names while here.
|
|
|
|
|
|
this lets us do the syncs once for a fill of the ring instead of
once for every packet put onto the ring. it mirrors how we try to
do things for tx.
|
|
|
|
|
|
we dont user config of the ring size, especially before attach time,
and the dmamem api takes care of rounding up to PAGE_SIZE if it needs
to.
|
|
|
|
|
|
makes it more consistent with the rest of the tree.
|
|
|
|
this is mostly work by kettenis and claudio, with further work from
me to make the transmit side from the stack mpsafe.
there's a watchdog issue that will be worked on in tree after this
change.
tested by hrvoje popovski and gregor best
ok mpi@ claudio@ deraadt@ jmatthew@
|
|
ok kettenis@
|
|
allows them.
|
|
tx rate retry table. This will hopefully make 11n mode work in very noisy
environments. iwm(4) already does the same.
ok kettenis@
|
|
tell the firmware to always try the first rate in the table first.
ok kettenis@
|
|
basically only the ioctls that Linux allows on the so-called "render nodes".
For now, it also allows DRM_IOCTL_GET_MAGIC and DRM_IOCTL_GEM_OPEN, as we
don't implement prime/dma-buf yet in OpenBSD. That still leaves a big gaping
hole, so they will be removed as soon as we can.
Based on a diff by robert@, who did all the heavy lifting by studying the
behaviour of the chromium GPU process, with some further suggestions by
deraadt@.
ok jsg@, deraadt@, robert@
|
|
|
|
in bsd.rd, and might uncover some bugs. Suggested by tedu@ and deraadt@.
ok sthen@ jasper@ deraadt@
|
|
Keep the modified chain pointer and pass it back to the calling code
so that it will get properly accounted for. Change it to m_pullup
since m_pulldown with a zero offset is just as good.
Tested by yasuoka@, myself and mxb at alumni ! chalmers ! se, thanks!
ok yasuoka, mpi
|
|
Only MCS 0 to 7 are supported for now.
Tested by many. There might still be outstanding issues but they now appear
to be rare. I'm putting this in so that additional fixes can be developed
and tested more easily if required. This diff is already quite large for
one commit.
ok deraadt
|
|
ok kettenis@
|
|
|