From: Cosmin GIRADU <cosmin.giradu@rcs-rds.ro>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: sched: use pinned timers
Date: Wed, 07 Jan 2015 12:06:59 +0200 [thread overview]
Message-ID: <54AD0543.1090806@rcs-rds.ro> (raw)
In-Reply-To: <20140926.002710.1595423408687413602.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]
On 26/09/14 07:27, David Miller wrote:
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Sat, 20 Sep 2014 18:01:30 -0700
>
>> From: Eric Dumazet <edumazet@google.com>
>>
>> While using a MQ + NETEM setup, I had confirmation that the default
>> timer migration ( /proc/sys/kernel/timer_migration ) is killing us.
>>
>> Installing this on a receiver side of a TCP_STREAM test, (NIC has 8 TX
>> queues) :
> ...
>> Current Qdiscs that benefit from this change are :
>>
>> netem, cbq, fq, hfsc, tbf, htb.
>>
>> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Looks great, applied, thanks Eric.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Hi Eric,
I saw that this patch didn't make it's way into the stable branches.
So I have two questions:
- Would it be safe to apply to linux-3.12.x stable?
- If yes, would there be any [noticeable] efects on a [pretty
complex] HTB setup? (I know, test and I'll see,
but if theory sais I won't, then there would be no point to
the test, would there?)
Thank you!
--
Cosmin GIRADU
OSS Engineer
RCS & RDS - Unified Services
Phone: +40-31-400-6323
Mobile: +40-77-020-0858
http://www.rcs-rds.ro
..........................................................................
Privileged/Confidential Information may be contained in this message. If
you are not the addressee indicated in this message (or responsible for
delivery of the message to such person), you may not copy or deliver
this message to anyone. In such a case, you should destroy this message
and kindly notify the sender by reply e-mail.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-07 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 1:01 [PATCH net-next] net: sched: use pinned timers Eric Dumazet
2014-09-26 4:27 ` David Miller
2015-01-07 10:06 ` Cosmin GIRADU [this message]
2015-01-07 15:45 ` Eric Dumazet
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=54AD0543.1090806@rcs-rds.ro \
--to=cosmin.giradu@rcs-rds.ro \
--cc=eric.dumazet@gmail.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