From: "Paul E. McKenney" <paulmck-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rp-hdFA07tZRcq1sMc9nBuxBA@public.gmane.org,
linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
ltt-dev-33AaDErTWvBVxDZ2/Zk0YoryAYyacSEB@public.gmane.org
Subject: LPC2011 Scaling Micro Conf
Date: Sun, 24 Apr 2011 17:45:04 -0700 [thread overview]
Message-ID: <20110425004504.GA14037@linux.vnet.ibm.com> (raw)
Hello!
Given the increasing numbers of CPUs on low-cost servers as well as
the appearance of SMP hand-held battery-powered devices, Linux Plumbers
2011 will feature a Scaling track, with topics including the following:
- What can the kernel do to help applications perform and scale better?
- What can applications do to help the kernel perform and scale better?
- Memory footprint:
+ 100MB here, 100MB there, pretty soon you are talking real memory!
+ Improving performance by decreasing icache and dcache footprint.
- Limits to scalability:
+ Technological limitations, especially hardware.
+ Complexity/maintainability limitations.
- Handling of non-CPU computational hardware (GPGPUs, crypto HW, etc.)
+ Can the kernel make good use of non-CPU computational hardware?
+ How best to enable user applications to use them?
- Dealing with the numerous remaining "little kernel locks"
The intended audience is developers interested in performance and
scalability throughout the Linux plumbing.
The deadline is April 30th. Please submit your proposals, whether to
Scaling or to other microconferences, at:
http://www.linuxplumbersconf.org/2011/ocw/events/LPC2011MC/proposals
The general track is also open for submissions until April 30th:
http://www.linuxplumbersconf.org/2011/ocw/events/LPC2011/proposals
Either way, we look forward to seeing your submissions!
Thanx, Paul
reply other threads:[~2011-04-25 0:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110425004504.GA14037@linux.vnet.ibm.com \
--to=paulmck-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=linaro-dev-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ltt-dev-33AaDErTWvBVxDZ2/Zk0YoryAYyacSEB@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rp-hdFA07tZRcq1sMc9nBuxBA@public.gmane.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).