|
|
InMTU/OutMTU (L2CA_ConfigReq/L2CA_ConfigRsp parameters)
Original Post: InMTU&OutMTU (SIG Forum) Date:
2000-04-07
The values to assign to InMTU and OutMTU (The parameters of
L2CA_ConfigReq and L2CA_ConfigRsp), depend upon the environment you
are working in:
- Embedded systems with limited buffer space don't want to assemble
large L2CAP packets so these would benefit from small MTUs.
- Systems passing large packets from higher layers want to be able to
encapsulate a whole packet, so in these cases the MTU should be
matched to the higher layer application/protocol packet size .
- Systems which have problems with latency (compressed video) may want
a small MTU so that they don't introduce large delays in the
segmentation and reassembly process.
Setting MTUs too small will introduce unnecessary overhead as a higher
proportion of bandwidth will be used by L2CAP headers. If you're just
doing a prototype system then small MTUs make it easier to test things as
you're sending less data. These are just some of the issues, but
considering them you should be able to see that there's really no standard
answer to what size MTU's to set, it varies by application and
environment. |
