From: "John Stoffel" <john@stoffel.org>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
John Stoffel <john@stoffel.org>, Eric Paris <eparis@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.36-rc7
Date: Fri, 8 Oct 2010 20:46:16 -0400 [thread overview]
Message-ID: <19631.47960.804661.384152@quad.stoffel.home> (raw)
In-Reply-To: <201010082303.17706.agruen@suse.de>
>>>>> "Andreas" == Andreas Gruenbacher <agruen@suse.de> writes:
Andreas> On Friday 08 October 2010 18:17:25 Tvrtko Ursulin wrote:
>> Doesn't really solve ordering inside groups so maybe we do not need
>> priorities at all just these three classes?
Andreas> Applications can easily make the priority they register with
Andreas> configurable (and default to something in their "range" if we
Andreas> define such ranges). Wouldn't this be enough?
What about conflicts, when two applications register with the same
priority? And then one of the them exits, dies, fails, and
re-registers itself.
Does it get the same slot back? Does it goto the end of the line? If
it's an HSM handling (or other content manipulation tool) what
happens?
These are the questions which need to be answered, and the ABI updated
to reflect these questions. Even if it's just "We don't care..." it
needs to be spelled out.
John
next prev parent reply other threads:[~2010-10-09 0:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 21:45 Linus Torvalds
2010-10-07 0:49 ` Stephen Rothwell
2010-10-08 15:05 ` James Bottomley
2010-10-07 16:10 ` Tvrtko Ursulin
2010-10-07 17:15 ` Tvrtko Ursulin
2010-10-07 17:33 ` Eric Paris
2010-10-07 18:07 ` Alan Cox
2010-10-07 17:49 ` Eric Paris
2010-10-08 12:06 ` Andreas Gruenbacher
2010-10-08 16:33 ` David Daney
2010-10-08 21:50 ` Andreas Gruenbacher
2010-10-08 21:59 ` H. Peter Anvin
2010-10-11 22:13 ` fanotify: disable fanotify syscalls Eric Paris
2010-10-08 16:38 ` Linux 2.6.36-rc7 Eric Paris
2010-10-08 21:45 ` Andreas Gruenbacher
2010-10-07 20:55 ` John Stoffel
2010-10-07 21:24 ` Eric Paris
2010-10-08 15:42 ` John Stoffel
2010-10-08 16:17 ` Tvrtko Ursulin
2010-10-08 16:41 ` Eric Paris
2010-10-18 11:01 ` Tvrtko Ursulin
2010-10-08 16:54 ` John Stoffel
2010-10-08 21:03 ` Andreas Gruenbacher
2010-10-09 0:46 ` John Stoffel [this message]
2010-10-07 19:28 ` Tejun Heo
2010-10-07 20:13 ` [dm-devel] " Milan Broz
2010-10-08 17:02 ` Tejun Heo
2010-10-10 11:56 ` Torsten Kaiser
2010-10-11 10:09 ` [PATCH wq#for-next] workqueue: fix HIGHPRI handling in keep_working() Tejun Heo
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=19631.47960.804661.384152@quad.stoffel.home \
--to=john@stoffel.org \
--cc=agruen@suse.de \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tvrtko.ursulin@sophos.com \
/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®