From: James Bottomley <James.Bottomley@SteelEye.com>
To: luben_tuikov@adaptec.com
Cc: Andrew Morton <akpm@osdl.org>, Jim Houston <jim.houston@ccur.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Dave Jones <davej@redhat.com>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH 2.6.12.5 1/2] lib: allow idr to be used in irq context
Date: Sun, 21 Aug 2005 22:15:40 -0500 [thread overview]
Message-ID: <1124680540.5068.37.camel@mulgrave> (raw)
In-Reply-To: <20050822003325.33507.qmail@web51613.mail.yahoo.com>
On Sun, 2005-08-21 at 17:33 -0700, Luben Tuikov wrote:
> No preallocation is done from IRQ context. Do not spread FUD.
> It seems to me that you're unaware how IDR works and unaware how
> the driver works.
Argumentum ad Hominem now ... we'll get them all eventually.
Since you won't post the usage code, just answer this: how does what
you're doing with idr differ from its originally designed consumer: the
posix timers which also do the idr_remove() in IRQ context?
To me it seems your argument applies to this case as well, but you
didn't quote it when asked for an example, so I assume there's some
difference that I don't understand.
James
next prev parent reply other threads:[~2005-08-22 3:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:03 [PATCH 2.6.12.5 1/2] lib: allow idr to be used in irq context Luben Tuikov
2005-08-17 16:01 ` Jim Houston
2005-08-21 8:25 ` Andrew Morton
2005-08-21 15:49 ` Luben Tuikov
2005-08-21 16:06 ` James Bottomley
2005-08-21 17:27 ` Luben Tuikov
2005-08-21 22:03 ` James Bottomley
2005-08-22 0:33 ` Luben Tuikov
2005-08-22 3:15 ` James Bottomley [this message]
2005-08-22 3:52 ` Andrew Morton
2005-08-22 14:28 ` James Bottomley
2005-08-22 16:51 ` Luben Tuikov
2005-08-22 21:53 ` James Bottomley
2005-08-22 22:09 ` Andrew Morton
2005-08-23 17:15 ` James Bottomley
2005-08-22 16:33 ` Luben Tuikov
2005-08-22 14:06 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2005-08-21 20:40 Luben Tuikov
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=1124680540.5068.37.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=jgarzik@pobox.com \
--cc=jim.houston@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.