From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH -next 2/3 v2] bnx2: Add prefetches to rx path.
Date: Thu, 06 May 2010 22:18:04 -0700 (PDT) [thread overview]
Message-ID: <20100506.221804.67909927.davem@davemloft.net> (raw)
In-Reply-To: <1273172293-10241-2-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Thu, 6 May 2010 11:58:13 -0700
> Add prefetches of the skb and the next rx descriptor to speed up rx path.
>
> Use prefetchw() for the skb [suggested by Eric Dumazet].
>
> The rx descriptor is in skb->data which is mapped for streaming mode DMA.
> Eric Dumazet pointed out that we should not prefetch the data before
> dma_sync. So we prefetch only if dma_sync is no_op on the system.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Also applied, thanks!
next prev parent reply other threads:[~2010-05-07 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 18:58 [PATCH -next 1/3 v2] bnx2: Add GRO support Michael Chan
2010-05-06 18:58 ` [PATCH -next 2/3 v2] bnx2: Add prefetches to rx path Michael Chan
2010-05-07 5:18 ` David Miller [this message]
2010-05-07 5:17 ` [PATCH -next 1/3 v2] bnx2: Add GRO support 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=20100506.221804.67909927.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.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).