From: Marc Giger <gigerstyle@gmx.ch>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4 on Alpha uninterruptible sleep of processes
Date: Sat, 13 Mar 2004 11:10:21 +0100 [thread overview]
Message-ID: <20040313111021.4af73b9e@hdg.gigerstyle.ch> (raw)
In-Reply-To: <20040313020141.B4021@den.park.msu.ru>
Hi Ivan,
On Sat, 13 Mar 2004 02:01:41 +0300
Ivan Kokshaysky <ink@jurassic.park.msu.ru> wrote:
> On Fri, Mar 12, 2004 at 09:52:15PM +0100, Marc Giger wrote:
> > Right now I'm recompiling the kernel. So you say this patch isn't a
> > fix but a test?
>
> Yes. That patch just reverts new alpha semaphore stuff which went
> into 2.6.4.
>
> > This time I have additionally "semaphore debugging" enabled,
> > perhaps it's useful for you.
>
> Thanks, this might be helpful.
Hmm, I couldn't boot the kernel with enabled "semaphore debugging". It
hangs directly after aboot. No messages, nothing. Do I something wrong?
Now I've booted 2.6.4 without debugging.
>
> > > The answer is here:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=397
> >
> > That's no answer, that's a statement:-) Do know the exactly reason
> > why it should be a bad idea? Is it mostly a bad idea on alpha?
>
> Hmm, I haven't discussed that with Richard, so I can't speak for him
> :-) IMHO, the benefits of the kernel preempt support in general are
> more than doubtful, the level of complexity that it adds to the kernel
> code is just unacceptable.
Ok, but I read somewhere exactly the opposite (lkml?).
The statement was something like the following: "Preempt doesn't need
much more infrastrucure in kernel code, because the needed locking
mechanism is already there (SMP)."
So I'm confused now:-) But I understand that every little more
complexity is not for free. More task switches etc...
Thank you for the infos.
greets
Marc
next prev parent reply other threads:[~2004-03-13 10:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 14:46 Marc Giger
2004-03-12 15:27 ` Ivan Kokshaysky
2004-03-12 15:41 ` Ivan Kokshaysky
2004-03-12 15:59 ` Marc Giger
2004-03-12 19:46 ` Ivan Kokshaysky
2004-03-12 20:52 ` Marc Giger
2004-03-12 23:01 ` Ivan Kokshaysky
2004-03-13 10:10 ` Marc Giger [this message]
2004-03-14 14:06 ` Ivan Kokshaysky
2004-03-14 18:52 ` Marc Giger
2004-03-15 11:51 ` Ivan Kokshaysky
2004-03-15 18:02 ` Marc Giger
2004-03-15 23:00 ` Ivan Kokshaysky
2004-03-16 12:23 ` Marc Giger
2004-03-16 17:00 ` Måns Rullgård
2004-03-12 20:53 ` Marc Giger
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=20040313111021.4af73b9e@hdg.gigerstyle.ch \
--to=gigerstyle@gmx.ch \
--cc=ink@jurassic.park.msu.ru \
--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
all inboxes | Powered by JetHome®