From: Vladimir Ivashchenko <hazard@francoudi.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: netdev@vger.kernel.org
Subject: Re: bond + tc regression ?
Date: Wed, 06 May 2009 21:45:18 +0300 [thread overview]
Message-ID: <1241635518.13702.37.camel@hazard2.francoudi.com> (raw)
In-Reply-To: <4A0105A8.3060707@cosmosbay.com>
On Wed, 2009-05-06 at 05:36 +0200, Eric Dumazet wrote:
> Ah, I forgot about one patch that could help your setup too (if using more than one
> cpu on NIC irqs of course), queued for 2.6.31
I have tried the patch. Didn't make a noticeable difference. Under 850
mbps HTB+sfq load, 2.6.29.1, four NICs / two bond ifaces, IRQ balancing,
the dual-core server has only 25% idle on each CPU.
What's interesting, the same 850mbps load, identical machine, but with
only two NICs and no bond, HTB+esfq, kernel 2.6.21.2 => 60% CPU idle.
2.5x overhead.
> (commit 6a321cb370ad3db4ba6e405e638b3a42c41089b0)
>
> You could post oprofile results to help us finding other hot spots.
>
>
> [PATCH] net: netif_tx_queue_stopped too expensive
>
> netif_tx_queue_stopped(txq) is most of the time false.
>
> Yet its cost is very expensive on SMP.
>
> static inline int netif_tx_queue_stopped(const struct netdev_queue *dev_queue)
> {
> return test_bit(__QUEUE_STATE_XOFF, &dev_queue->state);
> }
>
> I saw this on oprofile hunting and bnx2 driver bnx2_tx_int().
>
> We probably should split "struct netdev_queue" in two parts, one
> being read mostly.
>
> __netif_tx_lock() touches _xmit_lock & xmit_lock_owner, these
> deserve a separate cache line.
>
> Signed-off-by: Eric Dumazet <dada1@cosmosbay.com>
>
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 2e7783f..1caaebb 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -447,12 +447,18 @@ enum netdev_queue_state_t
> };
>
> struct netdev_queue {
> +/*
> + * read mostly part
> + */
> struct net_device *dev;
> struct Qdisc *qdisc;
> unsigned long state;
> - spinlock_t _xmit_lock;
> - int xmit_lock_owner;
> struct Qdisc *qdisc_sleeping;
> +/*
> + * write mostly part
> + */
> + spinlock_t _xmit_lock ____cacheline_aligned_in_smp;
> + int xmit_lock_owner;
> } ____cacheline_aligned_in_smp;
>
>
--
Best Regards,
Vladimir Ivashchenko
Chief Technology Officer
PrimeTel PLC, Cyprus - www.prime-tel.com
Tel: +357 25 100100 Fax: +357 2210 2211
next prev parent reply other threads:[~2009-05-06 18:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 15:45 bond + tc regression ? Vladimir Ivashchenko
2009-05-05 16:25 ` Denys Fedoryschenko
2009-05-05 16:31 ` Eric Dumazet
2009-05-05 17:41 ` Vladimir Ivashchenko
2009-05-05 18:50 ` Eric Dumazet
2009-05-05 23:50 ` Vladimir Ivashchenko
2009-05-05 23:52 ` Stephen Hemminger
2009-05-06 3:36 ` Eric Dumazet
2009-05-06 10:28 ` Vladimir Ivashchenko
2009-05-06 10:41 ` Eric Dumazet
2009-05-06 10:49 ` Denys Fedoryschenko
2009-05-06 18:45 ` Vladimir Ivashchenko [this message]
2009-05-06 19:30 ` Denys Fedoryschenko
2009-05-06 20:47 ` Vladimir Ivashchenko
2009-05-06 21:46 ` Denys Fedoryschenko
2009-05-08 20:46 ` Vladimir Ivashchenko
2009-05-08 21:05 ` Denys Fedoryschenko
2009-05-08 22:07 ` Vladimir Ivashchenko
2009-05-08 22:42 ` Denys Fedoryschenko
2009-05-17 18:46 ` Vladimir Ivashchenko
2009-05-18 8:51 ` Jarek Poplawski
2009-05-06 8:03 ` Ingo Molnar
2009-05-06 6:10 ` Jarek Poplawski
2009-05-06 10:36 ` Vladimir Ivashchenko
2009-05-06 10:48 ` Jarek Poplawski
2009-05-06 13:11 ` Vladimir Ivashchenko
2009-05-06 13:31 ` Patrick McHardy
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=1241635518.13702.37.camel@hazard2.francoudi.com \
--to=hazard@francoudi.com \
--cc=dada1@cosmosbay.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).