From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Anton Blanchard <anton@samba.org>
Subject: Re: 2.6.11-rc2-mm2
Date: Tue, 01 Feb 2005 20:17:33 +1100 [thread overview]
Message-ID: <41FF492D.8000700@yahoo.com.au> (raw)
In-Reply-To: <20050129131134.75dacb41.akpm@osdl.org>
Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc2/2.6.11-rc2-mm2/
>
>
>
>
> Changes since 2.6.11-rc2-mm1:
>
Just a couple of things:
> +task_size-is-variable.patch
> +use-mm_vm_size-in-exit_mmap.patch
>
I didn't hear back about my comments on this patch. I don't see
why MM_VM_SIZE should round up to the next PGDIR? This means
architecture implementations need to do the same thing, yes?
If MM_VM_SIZE means "the total address span of all top level page
tables an mm can contain", then OK. Otherwise it should probably
be left in the caller.
> Fixes for recent TASK_SIZE changes (these are still in flux)
>
^^^
Oh, I see :P
>
> -sched-isochronous-class-for-unprivileged-soft-rt-scheduling.patch
> -sched-account-rt_tasks-as-iso_ticks.patch
> +rlimit_rt_cpu.patch
> +rlimit_rt_cpu-fix.patch
> +rlimit_rt_cpu-sparc64-fix.patch
>
> Drop SCHED_ISO, add the rlimit which allows non-privileged users to gain
> limited RT scheduling policy.
>
At the risk of sounding like a luddite who doesn't want to see a
complex new userspace API introduced that we're forced to support
for the next 10 years... I have some valid concerns with the rt
limit patches.
A simple rlimit of RT priorities (a very well definied quantity,
in contrast the vague "CPU usage"), is easy, a patch exists, it
doesn't touch a single fastpath or add complexity, it immediately
addresses the concerns of the RT audio guys who started all this,
and can be used meaningfully by userspace systems that want to
control and limit *real* RT scheduling, and without breaking
defined userspace RT scheduling APIs, IMO would be a better place
to start.
If someone later comes along and wants the extra features and
quirks that these patches provide, then I'd be all for further work
and discussion.
And this isn't meant to be an attack on anyone - I'm aware that
the -mm tree is for testing and discussion and further progression
of patches.
next prev parent reply other threads:[~2005-02-01 9:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 21:11 2.6.11-rc2-mm2 Andrew Morton
2005-01-29 22:52 ` 2.6.11-rc2-mm2 Brice Goglin
2005-01-29 23:10 ` 2.6.11-rc2-mm2 Sean Neakums
2005-01-29 23:56 ` 2.6.11-rc2-mm2 Sean Neakums
2005-01-29 23:12 ` [patch 2.6.11-rc2-mm2] fix SERIAL_TXX9 dependencies Adrian Bunk
2005-01-29 23:16 ` Ralf Baechle
2005-01-30 0:15 ` [PATCH] Fix " Ralf Baechle
2005-01-30 13:05 ` Atsushi Nemoto
2005-01-30 15:45 ` Arnd Bergmann
2005-01-30 16:58 ` Ralf Baechle
2005-01-31 1:04 ` Atsushi Nemoto
2005-01-31 20:23 ` Arnd Bergmann
2005-01-31 20:53 ` Ralf Baechle
2005-01-31 21:29 ` Arnd Bergmann
2005-02-01 0:50 ` Atsushi Nemoto
2005-01-30 16:49 ` Ralf Baechle
2005-01-30 0:58 ` 2.6.11-rc2-mm2 - "freeing b_committed_data" Nathan Lynch
2005-01-30 1:06 ` Andrew Morton
2005-01-30 6:20 ` 2.6.11-rc2-mm2 Andrew Nelson
2005-01-30 11:03 ` 2.6.11-rc2-mm2 Rafael J. Wysocki
2005-01-31 21:15 ` 2.6.11-rc2-mm2 Andre Eisenbach
2005-01-31 21:46 ` 2.6.11-rc2-mm2 Laurent Riffard
2005-02-01 1:26 ` 2.6.11-rc2-mm2 Jim Nelson
2005-02-01 17:25 ` 2.6.11-rc2-mm2 Andre Eisenbach
2005-02-01 9:17 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-30 7:34 2.6.11-rc2-mm2 Paul Blazejowski
2005-01-30 7:56 ` 2.6.11-rc2-mm2 Andrew Morton
2005-01-30 10:54 ` 2.6.11-rc2-mm2 Christoph Hellwig
2005-01-30 10:57 ` 2.6.11-rc2-mm2 Christoph Hellwig
2005-01-30 12:00 ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 12:12 ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 20:35 ` 2.6.11-rc2-mm2 Paul Blazejowski
2005-01-30 23:00 ` 2.6.11-rc2-mm2 Roman Zippel
2005-01-30 23:10 ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 23:36 ` 2.6.11-rc2-mm2 Roman Zippel
2005-01-31 7:31 ` 2.6.11-rc2-mm2 Christoph Hellwig
2005-01-31 15:10 ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-31 15:16 ` 2.6.11-rc2-mm2 Roman Zippel
2005-01-31 19:42 ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-30 11:38 ` 2.6.11-rc2-mm2 Adrian Bunk
2005-01-31 14:51 ` 2.6.11-rc2-mm2 Christoph Hellwig
2005-01-30 20:45 ` 2.6.11-rc2-mm2 Paul Blazejowski
2005-01-31 19:37 ` 2.6.11-rc2-mm2 Chuck Harding
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=41FF492D.8000700@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--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