From: Eric Dumazet <dada1@cosmosbay.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
davem@davemloft.net, netdev@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org, andsve@gmail.com
Subject: Re: [Bugme-new] [Bug 8536] New: Kernel drops UDP packets silently when reading from certain proc file entries
Date: Fri, 25 May 2007 09:15:17 +0200 [thread overview]
Message-ID: <46568D05.9080309@cosmosbay.com> (raw)
In-Reply-To: <20070525065712.GA26619@gondor.apana.org.au>
Herbert Xu a écrit :
> On Fri, May 25, 2007 at 08:50:20AM +0200, Eric Dumazet wrote:
>> If this patch really helps, this means cond_resched_softirq()
>> doesnt work at all and should be fixed, or just zapped as it
>> is seldom used.
>
> cond_resched_softirq lets other threads run if they want to.
> It doesn't run pending softirq's at all. In fact, it doesn't
> even wake up ksoftirqd.
I am very glad you fixed /proc/net/tcp, but I would like to
understand why this cond_resched_softirq() even exist.
Its name and behavior dont match at all.
The only remaining use is in __release_sock().
Should we schedule threads, or ksoftirqd as well in this function ?
next prev parent reply other threads:[~2007-05-25 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705241948.l4OJmTAe031670@fire-2.osdl.org>
2007-05-24 19:59 ` [Bugme-new] [Bug 8536] New: Kernel drops UDP packets silently when reading from certain proc file entries Andrew Morton
2007-05-25 6:23 ` Herbert Xu
2007-05-25 6:50 ` Eric Dumazet
2007-05-25 6:57 ` Herbert Xu
2007-05-25 7:15 ` Eric Dumazet [this message]
2007-05-25 7:17 ` Herbert Xu
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=46568D05.9080309@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=akpm@linux-foundation.org \
--cc=andsve@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).