Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > IIUC, sender (desktop system) sends datagrams as fast as possible. > Receiver (tango board) drops around 24% of all datagrams. > I think this invalidates the theory that exhausting RX descriptors > wedges RX DMA. No, it doesn't. The bottleneck causing packet

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > On 02/08/2017 19:31, Mason wrote: > >> # iperf3 -c 172.27.64.45 -u -b 950M >> Connecting to host 172.27.64.45, port 5201 >> [ 4] local 172.27.64.1 port 55533 connected to 172.27.64.45 port 5201 >> [ ID] Interval Transfer Bandwidth Total

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

On 02/08/2017 22:02, Mason wrote: > I need to run the test slightly slower, to prevent packet loss > at the sender. # iperf3 -c 172.27.64.45 -u -b 0 -l 1000 Connecting to host 172.27.64.45, port 5201 [ 4] local 172.27.64.1 port 42607 connected to 172.27.64.45 port 5201 [ ID] Interval

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

On 02/08/2017 19:31, Mason wrote: > # iperf3 -c 172.27.64.45 -u -b 950M > Connecting to host 172.27.64.45, port 5201 > [ 4] local 172.27.64.1 port 55533 connected to 172.27.64.45 port 5201 > [ ID] Interval Transfer Bandwidth Total Datagrams > [ 4] 0.00-1.00 sec 102

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

On 02/08/2017 18:10, Måns Rullgård wrote: > ping -f is limited to 100 packets per second. > Use something like iperf in UDP mode instead. CLIENT: DESKTOP # iperf3 -c 172.27.64.45 -u -b 950M Connecting to host 172.27.64.45, port 5201 [ 4] local 172.27.64.1 port 55533 connected to 172.27.64.45

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > On 02/08/2017 18:10, Måns Rullgård wrote: > >> Mason writes: >> >>> On 02/08/2017 17:56, Måns Rullgård wrote: >>> What does the tango5 do if you flood it with packets faster than the kernel can keep up with? That would make it hit the end of the rx

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

On 02/08/2017 18:10, Måns Rullgård wrote: > Mason writes: > >> On 02/08/2017 17:56, Måns Rullgård wrote: >> >>> What does the tango5 do if you flood it with packets faster than the >>> kernel can keep up with? That would make it hit the end of the rx >>> chain, which is apparently what makes it

RE: [RFC PATCH v2 0/2] nb8800 suspend/resume support

From: Måns Rullgård > Sent: 02 August 2017 17:10 ... > ping -f is limited to 100 packets per second. Use something like iperf > in UDP mode instead. Or break a MAC driver so it just saturates the network. You might actually need bursts of traffic - otherwise the receiver will be continuously

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > On 02/08/2017 17:56, Måns Rullgård wrote: > >> Mason writes: >> >>> From my perspective, the older method does not work on newer chips :-) >> >> It does work on tango4. > > Agreed. > >> What does the tango5 do if you flood it with packets faster than the >>

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

On 02/08/2017 17:56, Måns Rullgård wrote: > Mason writes: > >> From my perspective, the older method does not work on newer chips :-) > > It does work on tango4. Agreed. > What does the tango5 do if you flood it with packets faster than the > kernel can keep up with? That would make it hit

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > On 02/08/2017 17:36, Måns Rullgård wrote: > >> Mason wrote: >> >>> Looking at the tango-specific integration, I note this nugget: >>> >>> 1.5.4 Stopping & Starting the DMA >>> >>> This feature has been added to allow the software to stop and start >>> the DMA

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

On 02/08/2017 17:36, Måns Rullgård wrote: > Mason wrote: > >> Looking at the tango-specific integration, I note this nugget: >> >> 1.5.4 Stopping & Starting the DMA >> >> This feature has been added to allow the software to stop and start >> the DMA without any issues. >> >> Procedure: >> 1-

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > On 02/08/2017 16:41, Mason wrote: > >> On 01/08/2017 18:32, Mason wrote: >> >>> I need suspend/resume support in the nb8800 driver. >>> On tango platforms, suspend loses all context (MMIO registers). >>> To make the task easy, we just close the device on

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

On 01/08/2017 18:32, Mason wrote: > I need suspend/resume support in the nb8800 driver. > On tango platforms, suspend loses all context (MMIO registers). > To make the task easy, we just close the device on suspend, > and open it again on resume. This requires properly resetting > the HW on