From: Ingo Oeser <netdev@axxeo.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Jeff Garzik <jgarzik@pobox.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] chelsio: more rx speedup
Date: Tue, 9 Jan 2007 09:42:03 +0100 [thread overview]
Message-ID: <200701090942.04197.netdev@axxeo.de> (raw)
In-Reply-To: <20070108112612.5f947357@dxpl.pdx.osdl.net>
Hi Stephen,
Stephen Hemminger schrieb:
> --- netdev-2.6.orig/drivers/net/chelsio/sge.c
> +++ netdev-2.6/drivers/net/chelsio/sge.c
[...]
> @@ -1043,45 +1046,42 @@ static void recycle_fl_buf(struct freelQ
> * be copied but there is no memory for the copy.
> */
> static inline struct sk_buff *get_packet(struct pci_dev *pdev,
> - struct freelQ *fl, unsigned int len,
> - int dma_pad, int skb_pad,
> - unsigned int copy_thres,
> - unsigned int drop_thres)
> + struct freelQ *fl, unsigned int len)
> {
> struct sk_buff *skb;
> - struct freelQ_ce *ce = &fl->centries[fl->cidx];
> + const struct freelQ_ce *ce = &fl->centries[fl->cidx];
>
> - if (len < copy_thres) {
> - skb = alloc_skb(len + skb_pad, GFP_ATOMIC);
> - if (likely(skb != NULL)) {
> - skb_reserve(skb, skb_pad);
> - skb_put(skb, len);
> - pci_dma_sync_single_for_cpu(pdev,
> - pci_unmap_addr(ce, dma_addr),
> - pci_unmap_len(ce, dma_len),
> - PCI_DMA_FROMDEVICE);
> - memcpy(skb->data, ce->skb->data + dma_pad, len);
> - pci_dma_sync_single_for_device(pdev,
> + if (len < copybreak) {
> + skb = alloc_skb(len + 2, GFP_ATOMIC);
> + if (!skb)
> + goto use_orig_buf;
> +
> + skb_reserve(skb, 2); /* align IP header */
Please use NET_IP_ALIGN here:
+ skb = alloc_skb(len + NET_IP_ALIGN, GFP_ATOMIC);
+ if (!skb)
+ goto use_orig_buf;
+
+ skb_reserve(skb, NET_IP_ALIGN);
> + skb_put(skb, len);
> + pci_dma_sync_single_for_cpu(pdev,
> pci_unmap_addr(ce, dma_addr),
> pci_unmap_len(ce, dma_len),
> PCI_DMA_FROMDEVICE);
> - } else if (!drop_thres)
> - goto use_orig_buf;
> -
> + memcpy(skb->data, ce->skb->data, len);
> + pci_dma_sync_single_for_device(pdev,
> + pci_unmap_addr(ce, dma_addr),
> + pci_unmap_len(ce, dma_len),
> + PCI_DMA_FROMDEVICE);
> recycle_fl_buf(fl, fl->cidx);
> return skb;
> }
>
> - if (fl->credits < drop_thres) {
> +use_orig_buf:
> + if (fl->credits < 2) {
Why 2? What does this magic number mean?
Regards
Ingo Oeser
next prev parent reply other threads:[~2007-01-09 8:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 19:07 [PATCH 0/3] chelsio driver changes Stephen Hemminger
2006-12-15 19:07 ` [PATCH 1/3] chelsio: fix error path Stephen Hemminger
2006-12-15 19:07 ` [PATCH 2/3] chelsio: NAPI speed improvement Stephen Hemminger
2006-12-15 19:07 ` [PATCH 3/3] chelsio: more receive cleanup Stephen Hemminger
2006-12-15 20:10 ` Francois Romieu
2006-12-15 22:55 ` Stephen Hemminger
2006-12-16 0:26 ` Francois Romieu
2006-12-16 1:28 ` Stephen Hemminger
2006-12-26 21:16 ` [PATCH 0/3] chelsio driver changes Jeff Garzik
2007-01-08 19:24 ` [PATCH 1/3] chelsio: error path fix Stephen Hemminger
[not found] ` <20070108112524.730e89f0@dxpl.pdx.osdl.net>
2007-01-08 19:26 ` [PATCH 3/3] chelsio: more rx speedup Stephen Hemminger
2007-01-09 8:42 ` Ingo Oeser [this message]
2007-01-09 18:26 ` Stephen Hemminger
2007-01-10 2:08 ` Divy Le Ray
2007-01-10 8:34 ` Ingo Oeser
2007-01-10 8:30 ` Ingo Oeser
2007-01-19 3:05 ` Jeff Garzik
2007-01-08 19:26 ` [PATCH 2/3] chelsio: NAPI speed improvement Stephen Hemminger
2007-01-19 3:05 ` Jeff Garzik
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=200701090942.04197.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
/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).