From: Eric Dumazet <dada1@cosmosbay.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] net/core/dst.c : Should'nt dst_run_gc() be more scalable and friendly ?
Date: Fri, 17 Aug 2007 10:31:13 +0200 [thread overview]
Message-ID: <20070817103113.e737c2d9.dada1@cosmosbay.com> (raw)
In-Reply-To: <20070817081522.GA16720@gondor.apana.org.au>
On Fri, 17 Aug 2007 16:15:22 +0800
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Fri, Aug 17, 2007 at 10:10:30AM +0200, Eric Dumazet wrote:
> >
> > Will a workqueue react the same in case of a DDOS situation,
> > where softirq could use all CPU cycles to handle incoming
> > packets and feed the GC list, and GC would never
> > have a chance to scan and free some items ?
>
> Well when that happens the softirqs will be deferred to
> ksoftirqd which should share the CPU fairly with the
> workqueue.
Thats nice :)
I'll code a workqueue based thing in about 10 days after my hollidays,
and perform DOS tests as well.
Thanks for the feedback.
>
> > About chunk processing, I did it on purpose, to not throw away
> > all CPU cache. Goal is to process entries, but not all of them
> > in a row, especially if we find many yet referenced entries
> > (and thus not candidates to freeing)
>
> I agree that chunks are desirable for a timer since you'd
> be hogging the CPU otherwise. However, if you went to a
> workqueue then it's less of a concern and would simplify
> things. In particular, you won't have to pick a good
> chunk size :)
prev parent reply other threads:[~2007-08-17 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 12:09 [RFC] net/core/dst.c : Should'nt dst_run_gc() be more scalable and friendly ? Eric Dumazet
2007-08-16 12:41 ` Herbert Xu
2007-08-16 13:36 ` Eric Dumazet
2007-08-16 13:59 ` Herbert Xu
2007-08-16 15:40 ` Eric Dumazet
2007-08-16 23:33 ` Herbert Xu
2007-08-17 8:10 ` Eric Dumazet
2007-08-17 8:15 ` Herbert Xu
2007-08-17 8:31 ` Eric Dumazet [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=20070817103113.e737c2d9.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=herbert@gondor.apana.org.au \
--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