From: Stephen Hemminger <shemminger@osdl.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] chelsio: more receive cleanup
Date: Fri, 15 Dec 2006 14:55:33 -0800 [thread overview]
Message-ID: <20061215145533.4cda3f23@freekitty> (raw)
In-Reply-To: <20061215201019.GA11385@electric-eye.fr.zoreil.com>
On Fri, 15 Dec 2006 21:10:19 +0100
Francois Romieu <romieu@fr.zoreil.com> wrote:
> Stephen Hemminger <shemminger@osdl.org> :
> [...]
> > --- linux-2.6.20-rc1.orig/drivers/net/chelsio/sge.c
> > +++ linux-2.6.20-rc1/drivers/net/chelsio/sge.c
> [...]
> > @@ -1059,37 +1062,33 @@ static void recycle_fl_buf(struct freelQ
> > * threshold and the packet is too big to copy, or (b) the packet should
> > * 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)
> > +static inline struct sk_buff *get_packet(struct pci_dev *pdev, 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 < copybreak) {
>
> If you are into cleanups, maybe add likely/unlikely (and remove the inline) ?
Why, you can't predict copybreak on off
>
> > + skb = alloc_skb(len + 2, GFP_ATOMIC);
> > + if (!skb)
> > + goto use_orig_buf;
> >
> > - 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,
> > + skb_reserve(skb, 2); /* align IP header */
>
> s/2/NET_IP_ALIGN/
This is wrong, NET_IP_ALIGN is for DMA buffers only. It is defined
as 0 for those platforms where DMA alignment is important. In this
case we are copying, so we want to force 2.
> Btw, since the driver supports netpoll, its blind enabling of interrupts
> in t1_poll() seems old-fashoined (see thread starting at
> http://lkml.org/lkml/2006/12/12/86)
>
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2006-12-15 22:56 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 [this message]
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
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=20061215145533.4cda3f23@freekitty \
--to=shemminger@osdl.org \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).