Hello!

This set of data frames you quoted are all full, and
are tightly interspaced.  It looks exactly like a TSO
frame, which we certainly set PSH on, but the TSO
engine is dropping it aparently.

I guess this is e1000.  Any e1000 internals experts reading
here who can comment on how e1000's TSO engine treats the
PSH flag?

Or it was two one-segment frames.

Before blaming on e1000 it would be easier to confirm that
linux never worked with MacOS X, except for those kernels which
had congestion avoidance mostly supppressed.

I.e. let's disable TSO in 2.6.9 and look.

Alexey