From: Thomas Graf <tgraf@suug.ch>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: design for TSO performance fix
Date: Fri, 28 Jan 2005 02:57:51 +0100 [thread overview]
Message-ID: <20050128015751.GT31837@postel.suug.ch> (raw)
In-Reply-To: <20050127163146.33b01e95.davem@davemloft.net>
* David S. Miller <20050127163146.33b01e95.davem@davemloft.net> 2005-01-27 16:31
> The basic idea is that we stop trying to build TSO frames
> in the actual transmit queue. Instead, TSO packets are
> built impromptu when we actually output packets on the
> transmit queue.
Sound great.
> static inline int tcp_skb_data_all_paged(struct sk_buff *skb)
> {
> return (skb->len == skb->data_len);
> }
You could also define this as (skb_headlen(skb) == 0)
> The logic is simple because if TSO is being done we know
> that all of the SKB data is paged (since SG+CSUM is a
> requirement for TSO). The one case where that
> invariant might fail is due to a routing change (previous
> device cannot do SG+CSUM, new device has full TSO capability)
> and that is handled via the tcp_skb_data_all_paged() checks.
I assume the case when reroute changes oif to a device no
longer capable of SG+CSUM stays the same and the skb remains
paged until dev_queue_xmit?
> My thinking is that whatever added expensive this new scheme
> has, is offset by the simplifications the rest of the TCP
> stack will have since it will no longer need to know anything
> about multiple MSS values and packet counts.
I think the overhead is really worth the complexity that can
be removed with these changes.
next prev parent reply other threads:[~2005-01-28 1:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 0:31 design for TSO performance fix David S. Miller
2005-01-28 0:51 ` Rick Jones
2005-01-28 0:58 ` David S. Miller
2005-01-28 1:31 ` Herbert Xu
2005-01-28 5:19 ` David S. Miller
2005-01-28 5:44 ` Herbert Xu
2005-01-28 19:28 ` David S. Miller
2005-01-29 10:12 ` Herbert Xu
2005-01-28 1:57 ` Thomas Graf [this message]
2005-02-01 23:04 ` David S. Miller
2005-01-28 6:25 ` Andi Kleen
2005-01-28 6:44 ` Nivedita Singhvi
2005-01-28 19:30 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050128015751.GT31837@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).