From: Michal Simek <monstr@monstr.eu>
To: netdev@vger.kernel.org
Subject: Add NAPI support to ll_temac driver
Date: Tue, 19 Apr 2011 11:35:15 +0200 [thread overview]
Message-ID: <4DAD5753.4040108@monstr.eu> (raw)
Hi,
I would like to try to add NAPI support for ll_temac and look if help us to
improve performance on Microblaze system. I would expect that bandwidth should
be increased.
We have the second non mainline driver which use tasklets and it provides better
performance than mainline driver but not so big that's why I think that NAPI
can increase performance.
Can you please point me to any driver which I could use as a template?
Or any developer guide to do so.
Do you know any other option how to improve driver performance on low speed cpu?
I have found that driver spends a lot of time on skb allocation and preallocated
SKBs help a little bit. I have done a test where I increased number of
preallocated BDs(SKBs) for rx to 35000 and disable new BD(SKB) allocation in
rx_irq. 35000 BDs is setup because I need them to successfully finish netperf
test. I have got 25% bandwidth increasing.
It will be also nice to be able to allocate several BDs(SKBs) which could be
faster than allocate them in sequence.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next reply other threads:[~2011-04-19 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 9:35 Michal Simek [this message]
2011-04-19 10:43 ` Add NAPI support to ll_temac driver Eric Dumazet
2011-04-19 12:25 ` Ben Hutchings
2011-04-19 12:48 ` Michal Simek
2011-04-19 13:13 ` Eric Dumazet
2011-04-19 13:14 ` Ben Hutchings
2011-04-19 13:18 ` Michal Simek
2011-04-20 11:06 ` Michal Simek
2011-04-20 12:47 ` Ben Hutchings
2011-04-19 13:21 ` Eric Dumazet
2011-04-19 12:26 ` Michal Simek
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=4DAD5753.4040108@monstr.eu \
--to=monstr@monstr.eu \
--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 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.