From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: pshelar@nicira.com, netdev@vger.kernel.org, edumazet@google.com,
jesse@nicira.com, bhutchings@solarflare.com, mirqus@gmail.com
Subject: Re: [PATCH net-next 0/3] v3 GRE: TCP segmentation offload
Date: Fri, 15 Feb 2013 20:53:57 -0500 (EST) [thread overview]
Message-ID: <20130215.205357.1130450552934768436.davem@davemloft.net> (raw)
In-Reply-To: <1360975955.19353.32.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 15 Feb 2013 16:52:35 -0800
> There is this "tx-nocache-copy" issue :
That scheme has so many system and device dependencies, but when
it does help it's nice to have.
Unfortunately I don't know the best way to proceed about that.
prev parent reply other threads:[~2013-02-16 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 19:44 [PATCH net-next 0/3] v3 GRE: TCP segmentation offload Pravin B Shelar
2013-02-15 20:18 ` David Miller
2013-02-16 0:52 ` Eric Dumazet
2013-02-16 1:41 ` Pravin Shelar
2013-02-16 1:43 ` Eric Dumazet
2013-02-16 1:53 ` David Miller [this message]
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=20130215.205357.1130450552934768436.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jesse@nicira.com \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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).