From: Eric Dumazet <eric.dumazet@gmail.com>
To: eilong@broadcom.com
Cc: David Miller <davem@davemloft.net>,
"bhutchings@solarflare.com" <bhutchings@solarflare.com>,
"pstaszewski@itcare.pl" <pstaszewski@itcare.pl>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] bnx2x: reduce skb truesize by 50%
Date: Sun, 13 Nov 2011 20:42:18 +0100 [thread overview]
Message-ID: <1321213338.17837.38.camel@edumazet-laptop> (raw)
In-Reply-To: <1321210419.3101.1.camel@lb-tlvb-eilong.il.broadcom.com>
Le dimanche 13 novembre 2011 à 20:53 +0200, Eilon Greenstein a écrit :
> I’m not sure I’m following the math over here. Assuming L1 is 64 bytes,
> we need up to 63 bytes to align the start address (assuming SLOB is
> being used) and additional (up to) 63 bytes at the end. That can sum up
> to 126 bytes am I missing something?
>
What do you really mean by aligning the end ?
How can both start and end of a frame can be aligned ?
If hardware needs extra room after the end of frame, then we already
have it (since we store struct skb_shared_info here)
I ran following patch and everything is fine here
diff --git a/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h b/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h
index aec7212..ddc94cc 100644
--- a/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h
+++ b/drivers/net/ethernet/broadcom/bnx2x/bnx2x.h
@@ -1188,8 +1188,8 @@ struct bnx2x {
/* Max supported alignment is 256 (8 shift) */
#define BNX2X_RX_ALIGN_SHIFT ((L1_CACHE_SHIFT < 8) ? \
L1_CACHE_SHIFT : 8)
- /* FW use 2 Cache lines Alignment for start packet and size */
-#define BNX2X_FW_RX_ALIGN (2 << BNX2X_RX_ALIGN_SHIFT)
+ /* FW use Cache line Alignment for start packet and size */
+#define BNX2X_FW_RX_ALIGN (1 << BNX2X_RX_ALIGN_SHIFT)
#define BNX2X_PXP_DRAM_ALIGN (BNX2X_RX_ALIGN_SHIFT - 5)
struct host_sp_status_block *def_status_blk;
next prev parent reply other threads:[~2011-11-13 19:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 15:57 Linux Route Cache performance tests Paweł Staszewski
2011-11-06 17:29 ` Eric Dumazet
2011-11-06 18:28 ` Paweł Staszewski
2011-11-06 18:48 ` Eric Dumazet
2011-11-06 19:20 ` Paweł Staszewski
2011-11-06 19:38 ` Eric Dumazet
2011-11-06 20:25 ` Paweł Staszewski
2011-11-06 21:26 ` Eric Dumazet
2011-11-06 21:57 ` Paweł Staszewski
2011-11-06 23:08 ` Eric Dumazet
2011-11-07 8:36 ` Paweł Staszewski
2011-11-07 9:08 ` Eric Dumazet
2011-11-07 9:16 ` Eric Dumazet
2011-11-07 22:12 ` Paweł Staszewski
2011-11-07 13:42 ` Ben Hutchings
2011-11-07 14:33 ` Eric Dumazet
2011-11-09 17:24 ` [PATCH net-next] ipv4: PKTINFO doesnt need dst reference Eric Dumazet
2011-11-09 21:37 ` David Miller
2011-11-09 22:03 ` Eric Dumazet
2011-11-10 0:29 ` [PATCH net-next] bnx2x: reduce skb truesize by 50% Eric Dumazet
2011-11-10 15:05 ` Eilon Greenstein
2011-11-10 15:27 ` Eric Dumazet
2011-11-10 16:27 ` Eilon Greenstein
2011-11-10 16:45 ` Eric Dumazet
2011-11-13 18:53 ` Eilon Greenstein
2011-11-13 19:42 ` Eric Dumazet [this message]
2011-11-13 20:08 ` Eilon Greenstein
2011-11-13 22:00 ` Eric Dumazet
2011-11-14 5:08 ` David Miller
2011-11-14 6:25 ` Eric Dumazet
2011-11-14 15:57 ` Eric Dumazet
2011-11-14 19:21 ` David 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=1321213338.17837.38.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
/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