From: Brian King <brking@linux.vnet.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: Santiago Leon <santil@linux.vnet.ibm.com>, netdev@vger.kernel.org
Subject: Re: [patch 04/20] ibmveth: Add tx_copybreak
Date: Thu, 19 Aug 2010 08:34:48 -0500 [thread overview]
Message-ID: <4C6D32F8.1020409@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100819072503.937364037@samba.org>
On 08/19/2010 02:25 AM, Anton Blanchard wrote:
> Use the existing bounce buffer if we send a buffer under a certain size.
> This saves the overhead of a TCE map/unmap.
>
> I can't see any reason for the wmb() in the bounce buffer case, if we need
> a barrier it will be before we call h_send_logical_lan but we have
> nothing in the common case. Remove it.
>
> Signed-off-by: Anton Blanchard <anton@samba.org>
> ---
>
> Index: powerpc.git/drivers/net/ibmveth.c
> ===================================================================
> --- powerpc.git.orig/drivers/net/ibmveth.c 2010-08-10 18:35:52.293272470 +1000
> +++ powerpc.git/drivers/net/ibmveth.c 2010-08-10 18:35:55.440741255 +1000
> @@ -117,6 +117,11 @@ MODULE_DESCRIPTION("IBM i/pSeries Virtua
> MODULE_LICENSE("GPL");
> MODULE_VERSION(ibmveth_driver_version);
>
> +static unsigned int tx_copybreak __read_mostly = 128;
Where did the 128 come from? I thought I heard the 2k value discussed in
the past.
Thanks,
Brian
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
next parent reply other threads:[~2010-08-19 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100819072456.317416634@samba.org>
[not found] ` <20100819072503.937364037@samba.org>
2010-08-19 13:34 ` Brian King [this message]
2010-08-23 0:09 [patch 00/20] ibmveth update Anton Blanchard
2010-08-23 0:09 ` [patch 04/20] ibmveth: Add tx_copybreak Anton Blanchard
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=4C6D32F8.1020409@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=netdev@vger.kernel.org \
--cc=santil@linux.vnet.ibm.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).