summaryrefslogtreecommitdiffstats
path: root/sys/arch/sgi/dev/if_iec.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Change users of IFQ_SET_MAXLEN() and IFQ_IS_EMPTY() to use the "new" API.patrick2020-07-101-2/+2
| | | | ok dlg@ tobhe@
* Fix memory leak in iec_get(). If MCLGET fails free the mbuf as well.claudio2017-07-191-1/+2
| | | | | Found by Ilja Van Sprundel OK bluhm@ deraadt@
* Always leave one free slot in the Tx ring to avoid ambiguity with ringvisa2017-02-111-3/+3
| | | | | head and tail in the interrupt handler. This fixes an old bug that causes a Tx stall when Tx ring gets full.
* Simplify ifq_deq_{begin,rollback,commit} sequence to ifq_dequeue.visa2017-02-111-9/+3
|
* move counting if_opackets next to counting if_obytes in if_enqueue.dlg2017-01-221-2/+1
| | | | | | | this means packets are consistently counted in one place, unlike the many and various ways that drivers thought they should do it. ok mpi@ deraadt@
* m_free() and m_freem() test for NULL. Simplify callers which had their ownjsg2016-11-291-3/+2
| | | | | | NULL tests. ok mpi@
* G/C IFQ_SET_READY().mpi2016-04-131-2/+1
|
* replace IFF_OACTIVE manipulation with mpsafe operations.dlg2015-11-251-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | there are two things shared between the network stack and drivers in the send path: the send queue and the IFF_OACTIVE flag. the send queue is now protected by a mutex. this diff makes the oactive functionality mpsafe too. IFF_OACTIVE is part of if_flags. there are two problems with that. firstly, if_flags is a short and we dont have any MI atomic operations to manipulate a short. secondly, while we could make the IFF_OACTIVE operates mpsafe, all changes to other flags would have to be made safe at the same time, otherwise a read-modify-write cycle on their updates could clobber the oactive change. instead, this moves the oactive mark into struct ifqueue and provides an API for changing it. there's ifq_set_oactive, ifq_clr_oactive, and ifq_is_oactive. these are modelled on ifsq_set_oactive, ifsq_clr_oactive, and ifsq_is_oactive in dragonflybsd. this diff includes changes to all the drivers manipulating IFF_OACTIVE to now use the ifsq_{set,clr_is}_oactive API too. ok kettenis@ mpi@ jmatthew@ deraadt@
* You only need <net/if_dl.h> if you're using LLADDR() or a sockaddr_dl.mpi2015-11-241-2/+1
|
* The only network driver needing <net/if_types.h> is upl(4) for IFT_OTHER.mpi2015-11-241-2/+1
|
* shuffle struct ifqueue so in flight mbufs are protected by a mutex.dlg2015-11-201-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the code is refactored so the IFQ macros call newly implemented ifq functions. the ifq code is split so each discipline (priq and hfsc in our case) is an opaque set of operations that the common ifq code can call. the common code does the locking, accounting (ifq_len manipulation), and freeing of the mbuf if the disciplines enqueue function rejects it. theyre kind of like bufqs in the block layer with their fifo and nscan disciplines. the new api also supports atomic switching of disciplines at runtime. the hfsc setup in pf_ioctl.c has been tweaked to build a complete hfsc_if structure which it attaches to the send queue in a single operation, rather than attaching to the interface up front and building up a list of queues. the send queue is now mutexed, which raises the expectation that packets can be enqueued or purged on one cpu while another cpu is dequeueing them in a driver for transmission. a lot of drivers use IFQ_POLL to peek at an mbuf and attempt to fit it on the ring before committing to it with a later IFQ_DEQUEUE operation. if the mbuf gets freed in between the POLL and DEQUEUE operations, fireworks will ensue. to avoid this, the ifq api introduces ifq_deq_begin, ifq_deq_rollback, and ifq_deq_commit. ifq_deq_begin allows a driver to take the ifq mutex and get a reference to the mbuf they wish to try and tx. if there's space, they can ifq_deq_commit it to remove the mbuf and release the mutex. if there's no space, ifq_deq_rollback simply releases the mutex. this api was developed to make updating the drivers using IFQ_POLL easy, instead of having to do significant semantic changes to avoid POLL that we cannot test on all the hardware. the common code has been tested pretty hard, and all the driver modifications are straightforward except for de(4). if that breaks it can be dealt with later. ok mpi@ jmatthew@
* arp_ifinit() is no longer needed.mpi2015-10-251-4/+1
|
* Fix an uninitialized variable found by Maxime Villard's Brainy.visa2015-09-181-5/+5
| | | | | | | While here, fix the size parameter of bus_dmamem_unmap() in iec_alloc_physical(). ok miod@
* Increment if_ipackets in if_input().mpi2015-06-241-3/+1
| | | | | | | Note that pseudo-drivers not using if_input() are not affected by this conversion. ok mikeb@, kettenis@, claudio@, dlg@
* Convert to if_input(), tested by jasper@.mpi2015-03-111-13/+5
|
* unifdef INETtedu2014-12-221-3/+1
|
* <netinet/in_systm.h> is no longer needed.mpi2014-07-221-7/+2
|
* Format string fixes and removal of -Wno-format for sgi. Based upon anmiod2014-05-191-2/+2
| | | | initial diff from jasper@
* Most network drivers include netinet/in_var.h, but apparently theybluhm2013-08-171-2/+1
| | | | | don't have to. Remove these include lines from sgi drivers. test jsing@
* When setting up the multicast filter, use the ac_multicnt field of the arpcommiod2012-05-221-3/+3
| | | | | struct to know if there are multicast entries, instead of counting the number of entries in the list. No functional change. From brad.
* Do not leak mbuf in the TX path when a TX error occurs; found the hard waymiod2010-03-151-16/+14
| | | | by syuu@; ok kettenis@
* Figure out the size of the SSRAM used as internal memory by the chip onmiod2009-11-081-29/+74
| | | | attach, print it, and decide how many RX descriptors to use accordingly.
* Align each RX descriptor to a 4KB boundary; fixes poor RX performance (chipmiod2009-11-031-4/+4
| | | | would stop RX operation if it had to cross a 4KB boundary during receive).
* A few cleanups and also reflect duplex state in mcr in addition to tcsr.miod2009-11-031-11/+19
|
* Got the RX threshold interrupt working, does not help RX performance though;miod2009-11-021-6/+10
| | | | | while there, silence overzealous messages when the TX empty interrupt fires before we disable it.
* A few fixes and improvements:miod2009-11-021-27/+29
| | | | | | | | - double the number of rx buffers. - copy packets of 104 bytes or less entirely in the tx descriptor, instead of only doing this for packets smaller than an Ethernet header. - correctly disable the rx threshold interrupt. Otherwise, one received frame every 64 would not be handled because we are not using this interrupt.
* Looks like I forgot to add files again. These are the most important filesmiod2009-11-011-0/+1372
for the new iec(4) driver. Reminded by brad@
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.