From: "Paweł Sikora" <pawel.sikora@agmk.net>
To: linux-kernel@vger.kernel.org
Subject: [3.13.2] list passed to list_sort() too long for efficiency.
Date: Wed, 12 Feb 2014 18:16:49 +0100 [thread overview]
Message-ID: <1799469.xr2i5c36Hj@localhost.localdomain> (raw)
Hi,
i've noticed on my server that dmesg contains following info:
(...)
[ 141.192868] FS-Cache: Loaded
[ 141.203008] FS-Cache: Netfs 'nfs' registered for caching
[ 1383.278845] Key type dns_resolver registered
[ 1383.293014] NFS: Registering the id_resolver key type
[ 1383.293027] Key type id_resolver registered
[ 1383.293028] Key type id_legacy registered
[ 3998.115273] perf samples too long (2502 > 2500), lowering
kernel.perf_event_max_sample_rate to 50100
[16855.582522] list passed to list_sort() too long for efficiency
could someone put some light on the last line?
BR,
Paweł.
please CC on reply.
--
gpg key fingerprint = 60B4 9886 AD53 EB3E 88BB 1EB5 C52E D01B 683B 9411
next reply other threads:[~2014-02-12 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 17:16 Paweł Sikora [this message]
[not found] ` <1392227186.1868.20.camel@joe-AO722>
2014-02-12 17:59 ` Paweł Sikora
2014-02-12 18:03 ` Dave Jones
2014-02-12 18:13 ` Paweł Sikora
2014-02-12 18:07 ` Joe Perches
2014-02-20 7:09 ` Dave Chinner
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=1799469.xr2i5c36Hj@localhost.localdomain \
--to=pawel.sikora@agmk.net \
--cc=linux-kernel@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
Powered by JetHome