Grazie mille. I will test it as time allows -- swamped.
Joe Buehler
Vincenzo Maffione wrote:
> Hi,
> This commit (fe13476b106ed1f4b517b1590e1dfb3f268b6e78) in the upstream
> netmap should have fixed the NS_MOREFRAG issue for ixgbe.
> If you happen give a try let us know.
>
> Cheers,
> Vincen
Hi,
This commit (fe13476b106ed1f4b517b1590e1dfb3f268b6e78) in the upstream
netmap should have fixed the NS_MOREFRAG issue for ixgbe.
If you happen give a try let us know.
Cheers,
Vincenzo
2018-03-21 21:40 GMT+01:00 Vincenzo Maffione :
> I see. Unfortunately this breaks the API, so I don't th
I see. Unfortunately this breaks the API, so I don't think we can accept it.
We should probably sum up the fragment lengths, remember which one was the
first descriptor and write the olinfo field when we process the last
descriptor ...
I hope this does not slow down the simpler case where NS_MOREFR
Attached is a patch that allows fragmented TX with the ixgbevf driver.
For the first TX buffer set the slot length to the full length of the frame and
make sure that the slot buffer is fully filled. For succeeding slots just set
the length to the amount of the buffer filled.
Not intended as th
If you could fix this I would appreciate it. My L1 TX performance for 64 byte
L2 frames drops significantly, from about 9 gigbits to 7 gigabits, when I use
buffers large enough to hold jumbo frames.
I will play with it a bit locally. One thing that occurs to me is to pass the
full frame lengt
2018-03-19 20:49 GMT+01:00 Joe Buehler :
> Vincenzo Maffione wrote:
>
> > To receive a frame larger than the RX buffer size you need multiple
> > netmap slots (as multiple descriptors are
> > used by the hardware), looking at the NS_MOREFRAG flag.
> > See the example code in utils/functional.c::rx
Vincenzo Maffione wrote:
> To receive a frame larger than the RX buffer size you need multiple
> netmap slots (as multiple descriptors are
> used by the hardware), looking at the NS_MOREFRAG flag.
> See the example code in utils/functional.c::rx_one().
This works fine -- thanks.
> Also TX may ha
First, please make sure to use the latest netmap from github.
Yes, drivers in general use 2K or 4K RX buffers regardless of the MTU or
netmap buffer size.
To receive a frame larger than the RX buffer size you need multiple netmap
slots (as multiple descriptors are
used by the hardware), looking at
Sorry, I should have added, this is LINUX if it matters.
Joe Buehler wrote:
> I am having difficulties with netmap over top of ixgbevf when attempting to
> use a large MTU (say 9000 bytes).
>
> Does the ixgbevf driver use 2048 byte buffers for RX regardless of the MTU or
> netmap buffer size?
>
