From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: bpoirier@suse.de, netdev@vger.kernel.org
Subject: Re: tx-nocache-copy performance
Date: Mon, 06 Jan 2014 16:20:24 -0500 (EST) [thread overview]
Message-ID: <20140106.162024.1656283406092977289.davem@davemloft.net> (raw)
In-Reply-To: <CA+mtBx_RH3v92Pmd_TYM=i0Anx-iG63762NPRSeCc1k98-Q6UQ@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
Date: Mon, 6 Jan 2014 12:59:59 -0800
> btw, I still believe it would be a win if we could use vmsplice to
> mitigate the copy altogether, unfortunately no one has yet to come up
> with an interface to reliably reclaim buffers :-(.
Indeed, this issue keeps coming up continually.
prev parent reply other threads:[~2014-01-06 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:27 tx-nocache-copy performance Benjamin Poirier
2014-01-06 20:57 ` Eric Dumazet
2014-01-06 21:13 ` Eric Dumazet
2014-01-06 23:20 ` [PATCH] net: Do not enable tx-nocache-copy by default Benjamin Poirier
2014-01-07 1:00 ` David Miller
2014-01-07 15:11 ` [PATCH v2] " Benjamin Poirier
2014-01-07 21:20 ` David Miller
2014-01-06 20:59 ` tx-nocache-copy performance Tom Herbert
2014-01-06 21:20 ` 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=20140106.162024.1656283406092977289.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bpoirier@suse.de \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).