From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>,
Davide Libenzi <davidel@xmailserver.org>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: mmotm 2009-02-14-00-49 uploaded -epoll busted.
Date: Tue, 17 Feb 2009 09:37:38 -0500 [thread overview]
Message-ID: <7379.1234881458@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 14 Feb 2009 00:51:41 PST." <200902140851.n1E8pfIN030501@imap1.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Sat, 14 Feb 2009 00:51:41 PST, akpm@linux-foundation.org said:
> The mm-of-the-moment snapshot 2009-02-14-00-49 has been uploaded to
The epoll patch series breaks nscd in some odd way. After it's started
in the /etc/rc* scripts, the rest of boot proceeds very slowly, smells like
nscd calls are hitting timeouts. Boot time went from ~1 minute to ~10 mins.
nscd is Fedora Rawhide nscd-2.9.90-3.x86_64, in case that matters...
Also, the series isn't bisectable right where it matters most, complaining
about implicit definitions of wake_up_nested...
epoll-keyed-wakeups-v2-add-__wake_up_locked_key-and-__wake_up_sync_key.patch
epoll-keyed-wakeups-v2-introduce-new-_poll-wakeup-macros.patch GOOD
epoll-keyed-wakeups-v3-introduce-new-_poll-wakeup-macros.patch BISECT BUSTED
epoll-keyed-wakeups-v2-make-sockets-use-keyed-wakeups.patch
epoll-keyed-wakeups-v2-teach-epoll-about-hints-coming-with-the-wakeup-key.patch
epoll-keyed-wakeups-v2-teach-epoll-about-hints-coming-with-the-wakeup-key-update.patch BAD
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-02-17 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200902140851.n1E8pfIN030501@imap1.linux-foundation.org>
2009-02-17 14:28 ` mmotm 2010-02-14-00-49 uploaded - synaptics breakage Valdis.Kletnieks
2009-02-17 14:37 ` Valdis.Kletnieks [this message]
2009-02-17 18:31 ` mmotm 2009-02-14-00-49 uploaded -epoll busted Davide Libenzi
2009-02-17 21:01 ` Valdis.Kletnieks
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=7379.1234881458@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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
all inboxes | Powered by JetHome®