lwip-users
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] [lwip] another pbuf question: why LINK_HLEN not reserverd

From: Lieverse, Paul
Subject: [lwip-users] [lwip] another pbuf question: why LINK_HLEN not reserverd for PBUF_LINK?
Date: Thu, 09 Jan 2003 01:20:57 -0000 
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--------------InterScan_NT_MIME_Boundary
Content-Type: multipart/alternative;
        boundary="----_=_NextPart_001_01C1C122.22B8CDB0"

------_=_NextPart_001_01C1C122.22B8CDB0
Content-Type: text/plain

Hi,

Another question regarding pbufs:

Why is PBUF_LINK_HLEN not added to the offset when a PBUF_LINK
pbuf is allocated? Seems logical:
PBUF_LINK_HLEN is then added for PBUF_LINK and all layers above;
PBUF_IP_HLEN for PBUF_IP and all layers above; and
PBUF_TRANSPORT_HLEN for PBUF_TRANSPORT (and all layers above).

Is there any reason for doing it this way? (apart from not breaking the
driver
implementations, which will probably rely on this by now...)

Paul

------_=_NextPart_001_01C1C122.22B8CDB0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>another pbuf question: why LINK_HLEN not reserverd for PBUF_LINK?</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">Hi,</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Another question regarding pbufs:</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Why is PBUF_LINK_HLEN not added to the offset when 
a PBUF_LINK</FONT>
<BR><FONT SIZE=2 FACE="Arial">pbuf is allocated? Seems logical:</FONT>
<BR><FONT SIZE=2 FACE="Arial">PBUF_LINK_HLEN is then added for PBUF_LINK and 
all layers above;</FONT>
<BR><FONT SIZE=2 FACE="Arial">PBUF_IP_HLEN for PBUF_IP and all layers above; 
and</FONT>
<BR><FONT SIZE=2 FACE="Arial">PBUF_TRANSPORT_HLEN for PBUF_TRANSPORT (and all 
layers above).</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Is there any reason for doing it this way? (apart 
from not breaking the driver</FONT>
<BR><FONT SIZE=2 FACE="Arial">implementations, which will probably rely on this 
by now...)</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Paul</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1C122.22B8CDB0--

--------------InterScan_NT_MIME_Boundary--

[This message was sent through the lwip discussion list.]
reply via email to
[Prev in Thread] Current Thread [Next in Thread]