[lkml]   [2009]   [Dec]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectOn "ratelimit: Use per ratelimit context locking"
Hi Ingo,

in pre 2.6.33-rc1 commit 979f693d you wrote: "I'd like to use
printk_ratelimit() in atomic context, but that's not possible right now
due to the spinlock usage this commit introduced more than a year ago:
717115e: printk ratelimiting rewrite".¹,²

By not possible, do you mean it would be an outright bug to call
printk_ratelimit in atomic context prior to 979f693d, or merely a
performance issue? If the former, under which circumstances would the
bug hit?

I'm asking because one of my commits actually introduced a
printk_ratelimit use in an interrupt handler shortly before 2.6.32 was
released. In my testing, it didn't occur to me that there might be a

Stefan Richter
-=====-==--= ==-- =-=--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-12-20 12:43    [W:0.041 / U:6.884 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site