On Mon, 2008-05-05 at 11:58 -0700, David Miller wrote:
quoted text
> From: Johannes Berg <johannes@sipsolutions.net>
> Date: Mon, 05 May 2008 19:57:34 +0200
>=20
> > NETIF_F_FRAGLIST I haven't understood, but it seems to apply mostly for
> > IP fragmentation?
>=20
> That's right.  It's for cards that can do IP fragmentation in
> hardware.

What does "do IP fragmentation in hardware" mean?

ip_output.c says:

 *      This IP datagram is too large to be sent in one piece.  Break it up=
 into
 *      smaller pieces (each of size equal to IP header plus
 *      a block of the data of the original IP data part) that will yet fit=
 in a
 *      single device frame, and queue such a frame for sending.

and later

                        /* Prepare header of the next frame,
                         * before previous one went down. */

so that seems to indicate that if the hardware just sends it all out in
the right order it'll be fine.

So the point is that the hardware will have to split it up into ethernet
frames on the IP boundaries?

johannes