From: Felipe Balbi <balbi@ti.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 3/4] net: ethernet: cpsw: split out IRQ handler
Date: Fri, 2 Jan 2015 21:02:38 -0600 [thread overview]
Message-ID: <20150103030238.GA19959@saruman> (raw)
In-Reply-To: <CAA93jw4BckMYOz_fUMVkW8m1YVO8uGjsb1srrhiF-meDoiD1WA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]
Hi,
On Fri, Jan 02, 2015 at 02:56:36PM -0800, Dave Taht wrote:
> On Fri, Jan 2, 2015 at 11:03 AM, Felipe Balbi <balbi@ti.com> wrote:
> > Hi,
> >
> > (please use reply-all to keep mailing lists in Cc, also avoid
> > top-posting)
>
> I am trying not to read netdev right now... and failing, obviously.
oops :-)
> > On Fri, Jan 02, 2015 at 10:58:29AM -0800, Dave Taht wrote:
> >> The beaglebone only has a 100mbit phy, so you aren't going to get more
> >> than that.
> >
> > very true :-) Still, with AM437x SK which is definitely GigE, I'm
> > getting 201Mbits/sec.
> >
> >> (so do a lot of IoT devices).
> >>
> >> So you have the two patches that went by on BQL and on NAPI for the beagle?
> >
> > no, got any pointers ?
>
> the relevant thread was "am335x: cpsw: phy ignores max-speed setting"
>
> and the initial very small BQL enablement patch was here:
>
> https://patchwork.ozlabs.org/patch/407640/
I'll test it out, sure.
> (it needed a saner treatment of a failure to dma something in
> cpsw_tx_packet_submit - the patch as is has also been part of nelsons
> trees for the beaglebone for a while)
>
> But it was rightly pointed out later in the thread that this change
>
> +#define CPSW_POLL_WEIGHT 16
>
> made for the biggest part of the improvement, and someone else on the
> thread proposed handling that more dynamically for 100mbit phys with
> another patch (that I can't find at the moment)
>
> ... but the root cause of the excessive latency in this driver was the
> single tx/rx dma queue, which you are addressing in your patch set.
I still think there's a lot of work pending for CPSW, the think slows to
a crawl and takes a lot of CPU for something that should be mostly
handled by DMA. I can very easily get 85% CPU usage with iperf.
> So if you glop on more of the above, mo better, perhaps you will win
> bigger.
>
> I will try to slice out some time to boot up a beagle on net-next next week.
my patches aren't applied yet, however.
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-03 3:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 18:10 [PATCH 0/4] net: cpsw: fix hangs and improve IRQ handling Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 18:10 ` [PATCH 1/4] net: ethernet: cpsw: fix hangs with interrupts Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 18:10 ` [PATCH 2/4] net: ethernet: cpsw: unroll IRQ request loop Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 18:10 ` [PATCH 3/4] net: ethernet: cpsw: split out IRQ handler Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
[not found] ` <CAA93jw7qyZjdHGKXjiBhiYp4BWBFrUFM6FF-Lzc0i7eOnM6cNg@mail.gmail.com>
2015-01-02 18:55 ` Felipe Balbi
2015-01-02 18:55 ` Felipe Balbi
[not found] ` <CAA93jw7=aFM3yQLO+vtN4uHW2gMnfNaY=BdbA+b0WYq-0+gSYQ@mail.gmail.com>
2015-01-02 19:03 ` Felipe Balbi
2015-01-02 19:03 ` Felipe Balbi
2015-01-02 22:56 ` Dave Taht
2015-01-03 3:02 ` Felipe Balbi [this message]
2015-01-02 18:10 ` [PATCH 4/4] net: ethernet: cpsw: don't requests IRQs we don't use Felipe Balbi
2015-01-02 18:10 ` Felipe Balbi
2015-01-02 21:45 ` [PATCH 0/4] net: cpsw: fix hangs and improve IRQ handling David Miller
2015-01-02 21:53 ` Felipe Balbi
2015-01-02 21:53 ` Felipe Balbi
2015-01-02 22:04 ` 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=20150103030238.GA19959@saruman \
--to=balbi@ti.com \
--cc=dave.taht@gmail.com \
--cc=linux-omap@vger.kernel.org \
--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.