RE: Problems with tg3 driver after lowering the MTU

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Templin, Fred L
Date: Thursday, January 21, 2010 - 4:02 pm

Ben,


In RFC1122, EMTU_S (i.e., the MTU) and EMTU_R (i.e., the
MRU) are maintained separately and are not specified as
dependent on one another directly. Intuitively however,
the relationship MTU <= MRU seems appropriate, and consistent
with a number of specs that require the reassembly size to
be no smaller than the interface MTU. The term "MRU" itself
came from RFC1661 (PPP) where it is the MRU and not MTU that
is negotiated.

So I see evidence to support the assertion that MTU <= MRU,
but I don't see much evidence to support the assertion that
MTU == MRU. Besides, if a packet arrives that is larger
than MTU but no larger than MRU, why throw away good data?

Fred
fred.l.templin@boeing.com
 

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Problems with tg3 driver after lowering the MTU, Szilveszter Ordog, (Thu Jan 21, 8:21 am)
Re: Problems with tg3 driver after lowering the MTU, Ben Hutchings, (Thu Jan 21, 8:27 am)
Re: Problems with tg3 driver after lowering the MTU, Szilveszter Ordog, (Thu Jan 21, 8:42 am)
RE: Problems with tg3 driver after lowering the MTU, Templin, Fred L, (Thu Jan 21, 10:47 am)
RE: Problems with tg3 driver after lowering the MTU, Ben Hutchings, (Thu Jan 21, 11:30 am)
RE: Problems with tg3 driver after lowering the MTU, Templin, Fred L, (Thu Jan 21, 4:02 pm)