Linux-kernel mailing list archive 1999-22,: Re: zero-copy TCP fileserving

# Re: zero-copy TCP fileserving

Alan Cox (alan@lxorguk.ukuu.org.uk)
Fri, 4 Jun 1999 13:49:51 +0100 (BST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Richard Gooch: "Re: zero-copy TCP fileserving"
- Previous message: DAVID BALAZIC: "Re: Large tmp files, async flush and still lots of I/O?"
- Next in thread: Richard Gooch: "Re: zero-copy TCP fileserving"
- Reply: Richard Gooch: "Re: zero-copy TCP fileserving"

> > As most (if not all) network drivers do load the entire frame onto the
> > card before beginning transmission, this is a possibility.
>
> Linus has pointed out that good cards fetch the data from memory as it
> is transmitted (is this true?) so I'll eat my words before everyone else
> does. :-)

Often it isnt true. They send one frame while fetching the next from
main memory. This avoids tons of crap packets caused by PCI bus latency
and the like but has almost identical performance under real I/O conditions

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Richard Gooch: "Re: zero-copy TCP fileserving"
- Previous message: DAVID BALAZIC: "Re: Large tmp files, async flush and still lots of I/O?"
- Next in thread: Richard Gooch: "Re: zero-copy TCP fileserving"
- Reply: Richard Gooch: "Re: zero-copy TCP fileserving"