From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Joe Lawrence <joe.lawrence@stratus.com>
Cc: Tejun Heo <tj@kernel.org>,
netdev@vger.kernel.org, Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH] team: add rescheduling jiffy delay on !rtnl_trylock
Date: Sun, 5 Oct 2014 07:08:55 -0700 [thread overview]
Message-ID: <20141005140855.GO5015@linux.vnet.ibm.com> (raw)
In-Reply-To: <54313F34.8090801@stratus.com>
On Sun, Oct 05, 2014 at 08:53:08AM -0400, Joe Lawrence wrote:
> On 10/04/2014 10:13 PM, Tejun Heo wrote:
> > Hello,
> >
> > On Sat, Oct 04, 2014 at 01:37:32AM -0700, Paul E. McKenney wrote:
> >> FWIW, there is a cond_resched_rcu_qs() that should be going into the next
> >> merge window that could be used in place of the above two lines. This is
> >> commit bde6c3aa9930 in -tip.
> >
> > That sounds even better.
> >
> > Joe, can you please send a patch with proper SOB and description?
> >
> > Thanks.
>
> New patch tested and posted on lkml w/everyone CC'd.
>
> I wasn't sure if cond_resched_rcu_qs will be backported, so how should
> -stable handle this condition?
If it is needed to backport a fix, it can of course be backported.
The various -stable maintainers also have the option of avoiding
the need for a backport by expanding it inline. I am happy to let
them choose. ;-)
Thanx, Paul
next prev parent reply other threads:[~2014-10-05 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 15:54 [PATCH] team: add rescheduling jiffy delay on !rtnl_trylock Joe Lawrence
2014-09-29 16:06 ` Tejun Heo
2014-10-02 6:43 ` Paul E. McKenney
2014-10-03 19:37 ` Joe Lawrence
2014-10-04 8:37 ` Paul E. McKenney
2014-10-05 2:13 ` Tejun Heo
2014-10-05 12:53 ` Joe Lawrence
2014-10-05 14:08 ` Paul E. McKenney [this message]
2014-10-05 16:11 ` Tejun Heo
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=20141005140855.GO5015@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=jiri@resnulli.us \
--cc=joe.lawrence@stratus.com \
--cc=netdev@vger.kernel.org \
--cc=tj@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.