From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Denis Vlasenko <vda@ilport.com.ua>,
Arjan van de Ven <arjan@infradead.org>,
Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: kmalloc without GFP_xxx?
Date: Wed, 29 Jun 2005 17:54:36 +0200 [thread overview]
Message-ID: <20050629155436.GD2130@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0506291141090.22775@localhost.localdomain>
On Wed, 29 June 2005 11:48:25 -0400, Steven Rostedt wrote:
> On Wed, 29 Jun 2005, Jörn Engel wrote:
>
> > All nice and well. But still, for the sake of simplicity and me not
> > wanting to think, I prefer always using spin_lock_irqsave for
> > everything. Since when should I stop and think about my own code?
>
> OK, I use spin_lock_irqsave first, and then I only use spin_lock when I
> already know interrupts are off. But the locks I usually use are used by
> interrupts and that is reason enough to use it. I wouldn't use the
> _irqsave for simplicity, I use it since I still believe it keeps latency
> down for SMP.
Ok, before even more people get confused - I was joking. Simple code
is obviously a good thing to have. Not thinking about code, well...
> > In fact, why don't we all sit down and start using KCSP for kernel
> > hacking? ;)
>
> Naw, I'm doing my PhD on implemting Linux drivers in SmallTalk. That will
> make everybody happy!
... but it appears as if you got the joke.
Jörn
--
Public Domain - Free as in Beer
General Public - Free as in Speech
BSD License - Free as in Enterprise
Shared Source - Free as in "Work will make you..."
next prev parent reply other threads:[~2005-06-29 15:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 11:02 Denis Vlasenko
2005-06-29 11:15 ` Jens Axboe
2005-06-29 11:18 ` Denis Vlasenko
2005-06-29 11:25 ` Jens Axboe
2005-06-29 11:15 ` Arjan van de Ven
2005-06-29 11:20 ` Denis Vlasenko
2005-06-29 11:37 ` Arjan van de Ven
2005-06-29 13:44 ` Steven Rostedt
2005-06-29 14:14 ` Denis Vlasenko
2005-06-29 14:23 ` Jörn Engel
2005-06-29 14:53 ` Steven Rostedt
2005-06-29 15:10 ` Jörn Engel
2005-06-29 15:48 ` Steven Rostedt
2005-06-29 15:54 ` Jörn Engel [this message]
2005-06-29 16:04 ` Steven Rostedt
2005-06-29 15:12 ` Oliver Neukum
2005-06-29 16:48 ` Timur Tabi
2005-06-29 17:22 ` Steven Rostedt
2005-06-29 17:43 ` Richard B. Johnson
2005-06-29 18:07 ` Steven Rostedt
2005-06-30 7:52 ` Denis Vlasenko
2005-06-30 8:05 ` Steven Rostedt
2005-06-30 1:02 ` Benjamin Herrenschmidt
2005-06-30 6:02 ` Steven Rostedt
2005-06-29 20:28 Manfred Spraul
2005-06-29 20:44 Manfred Spraul
2005-06-30 5:57 ` Steven Rostedt
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=20050629155436.GD2130@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=arjan@infradead.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=vda@ilport.com.ua \
/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®