From: Thomas Graf <tgraf@suug.ch>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, mroos@linux.ee,
herbert@gondor.apana.org.au
Subject: Re: [PATCH net-next] rhashtable: Allow other tasks to be scheduled in large lookup loops
Date: Fri, 17 Jul 2015 10:50:21 +0200 [thread overview]
Message-ID: <20150717085021.GA14796@pox.localdomain> (raw)
In-Reply-To: <1437121713.1026.22.camel@edumazet-glaptop2.roam.corp.google.com>
On 07/17/15 at 10:28am, Eric Dumazet wrote:
> On Fri, 2015-07-17 at 10:24 +0200, Eric Dumazet wrote:
>
> > Please simply use cond_resched() without counting and magic value.
Done
> Also use cond_resched() in insert and delete phases ?
When I tried that it made the walker duplicates disappear which weakens
the test case a little bit but it's probably safer this way. I'll include
it in the v2.
prev parent reply other threads:[~2015-07-17 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 8:07 [PATCH net-next] rhashtable: Allow other tasks to be scheduled in large lookup loops Thomas Graf
2015-07-17 8:24 ` Eric Dumazet
2015-07-17 8:28 ` Eric Dumazet
2015-07-17 8:50 ` Thomas Graf [this message]
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=20150717085021.GA14796@pox.localdomain \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=mroos@linux.ee \
--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