Hi,
On 01/04/2015 11:13 AM, Helmut Sim wrote:
> In such case, a modified api should not require to set the ip_hdr
> total_length field, which is 16 bits.
> The HW will assign the correct packet length for each transmitted IP
> packet which is l3_len+l4_len+mss (except of the last segment which may
correct.
In such case, a modified api should not require to set the ip_hdr
total_length field, which is 16 bits.
The HW will assign the correct packet length for each transmitted IP packet
which is l3_len+l4_len+mss (except of the last segment which may be smaller
than mss).
Sim
On Sun, Jan 4, 20
On Sun, Jan 4, 2015 at 10:50 AM, Helmut Sim wrote:
> Hi Alex and Olivier,
>
> Alex, I made the test and the segmentation is not at the IP level (i.e.
> each packet ip total length indicated the mss length), hence the 16 bits
> total length limitation is not relevant here.
>
Oliver thanks for rep
Hi Alex and Olivier,
Alex, I made the test and the segmentation is not at the IP level (i.e.
each packet ip total length indicated the mss length), hence the 16 bits
total length limitation is not relevant here.
I went over the 82599 datasheet and as Olivier mentioned it is a 18 bits
field, hence
Hi Helmut,
On 12/17/2014 08:17 AM, Helmut Sim wrote:
> While working on TSO based solution I faced the following two questions:
>
> 1.
> is there a maximum pkt_len to be used with TSO?, e.g. let's say if
> seg_sz
> is 1400 can the entire segmented pkt be 256K (higer than 64
thanks. i will check this
On Tue, Dec 16, 2014 at 4:04 PM, Alex Markuze wrote:
>
>
>
> On Tue, Dec 16, 2014 at 2:24 PM, Helmut Sim wrote:
>>
>> Thanks Alex,
>>
>> So i probably miss something...
>> what you are saying is correct for IP segmentation where the segmentation
>> is at the IP level, a
On Tue, Dec 16, 2014 at 2:24 PM, Helmut Sim wrote:
>
> Thanks Alex,
>
> So i probably miss something...
> what you are saying is correct for IP segmentation where the segmentation
> is at the IP level, and all segments are identified according to the
> Identification field in the IP header.
>
> Ho
Thanks Alex,
So i probably miss something...
what you are saying is correct for IP segmentation where the segmentation
is at the IP level, and all segments are identified according to the
Identification field in the IP header.
However in TCP segmentation the segments are at the TCP level (isn't i
On Mon, Dec 15, 2014 at 10:20 PM, Helmut Sim wrote:
>
> Hi,
>
> While working on TSO based solution I faced the following two questions:
>
> 1.
> is there a maximum pkt_len to be used with TSO?, e.g. let's say if seg_sz
> is 1400 can the entire segmented pkt be 256K (higer than 64K) ?, then the
>
Hi,
While working on TSO based solution I faced the following two questions:
1.
is there a maximum pkt_len to be used with TSO?, e.g. let's say if seg_sz
is 1400 can the entire segmented pkt be 256K (higer than 64K) ?, then the
driver gets a list of chanined mbufs while the first mbuf is set to T
10 matches
Mail list logo
