From: Brian King <brking@linux.vnet.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
santil@linux.vnet.ibm.com, rcjenn@linux.vnet.ibm.com
Subject: Re: [PATCH 1/4] ibmveth: Enable TCP checksum offload
Date: Thu, 19 Jul 2007 08:35:14 -0500 [thread overview]
Message-ID: <469F6892.2020908@linux.vnet.ibm.com> (raw)
In-Reply-To: <469E9510.7060703@garzik.org>
Jeff Garzik wrote:
> Brian King wrote:
>> This patchset enables TCP checksum offload support for IPV4
>> on ibmveth. This completely eliminates the generation and checking of
>> the checksum for packets that are completely virtual and never
>> touch a physical network. A simple TCP_STREAM netperf run on
>> a virtual network with maximum mtu set yielded a ~30% increase
>> in throughput. This feature is enabled by default on systems that
>> support it, but can be disabled with a module option.
>>
>> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
>
> this should be controllable purely via ethtool...
I'll remove the module parameter and resend.
>> struct ibmveth_rx_q_entry {
>> u16 toggle : 1;
>> u16 valid : 1;
>> - u16 reserved : 14;
>> + u16 reserved : 4;
>> + u16 no_csum : 1;
>> + u16 csum_good : 1;
>> + u16 reserved2 : 8;
>> u16 offset;
>
> As a general rule, it would be nice to start moving away from bitfields
> in this driver
I'll take a look at that for a future cleanup patch.
Thanks,
Brian
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Brian King <brking@linux.vnet.ibm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linuxppc-dev@ozlabs.org, rcjenn@linux.vnet.ibm.com,
santil@linux.vnet.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] ibmveth: Enable TCP checksum offload
Date: Thu, 19 Jul 2007 08:35:14 -0500 [thread overview]
Message-ID: <469F6892.2020908@linux.vnet.ibm.com> (raw)
In-Reply-To: <469E9510.7060703@garzik.org>
Jeff Garzik wrote:
> Brian King wrote:
>> This patchset enables TCP checksum offload support for IPV4
>> on ibmveth. This completely eliminates the generation and checking of
>> the checksum for packets that are completely virtual and never
>> touch a physical network. A simple TCP_STREAM netperf run on
>> a virtual network with maximum mtu set yielded a ~30% increase
>> in throughput. This feature is enabled by default on systems that
>> support it, but can be disabled with a module option.
>>
>> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
>
> this should be controllable purely via ethtool...
I'll remove the module parameter and resend.
>> struct ibmveth_rx_q_entry {
>> u16 toggle : 1;
>> u16 valid : 1;
>> - u16 reserved : 14;
>> + u16 reserved : 4;
>> + u16 no_csum : 1;
>> + u16 csum_good : 1;
>> + u16 reserved2 : 8;
>> u16 offset;
>
> As a general rule, it would be nice to start moving away from bitfields
> in this driver
I'll take a look at that for a future cleanup patch.
Thanks,
Brian
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
next prev parent reply other threads:[~2007-07-19 13:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 15:17 [PATCH 1/4] ibmveth: Enable TCP checksum offload Brian King
2007-07-17 15:17 ` [PATCH 2/4] ibmveth: Implement ethtool hooks to enable/disable " Brian King
2007-07-17 15:17 ` Brian King
2007-07-18 22:33 ` Jeff Garzik
2007-07-18 22:33 ` Jeff Garzik
2007-07-17 15:18 ` [PATCH 3/4] ibmveth: Add ethtool TSO handlers Brian King
2007-07-17 15:18 ` Brian King
2007-07-17 15:18 ` [PATCH 4/4] ibmveth: Add ethtool driver stats hooks Brian King
2007-07-17 15:18 ` Brian King
2007-07-18 22:34 ` Jeff Garzik
2007-07-18 22:34 ` Jeff Garzik
2007-07-18 22:32 ` [PATCH 1/4] ibmveth: Enable TCP checksum offload Jeff Garzik
2007-07-18 22:32 ` Jeff Garzik
2007-07-19 13:35 ` Brian King [this message]
2007-07-19 13:35 ` Brian King
-- strict thread matches above, loose matches on Subject: below --
2007-07-19 15:48 Brian King
2007-07-19 15:48 Brian King
2007-07-19 15:48 Brian King
2007-07-17 15:17 Brian King
2007-07-17 15:17 Brian King
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=469F6892.2020908@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=jeff@garzik.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=rcjenn@linux.vnet.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.