Messages in this thread | | | Subject | Re: vmalloc on 2.4.x on ia64 | Date | Thu, 5 Apr 2001 01:28:49 +0100 (BST) | From | Alan Cox <> |
| |
> I am calling during initialization only from detect() entry point. > But I guess, before the detect() is called, scsi layer acquires > the io_request_lock. So, you mean to say that I need to release it
That depends if your driver is doing old or new style initialization
> before calling vmalloc() ? I was doing the same thing on 2.2.x > and even on 2.4.0 and it was working fine and now suddenly > it stopped working on 2.4.2. So what are the guidelines for using > vmalloc() if we want to use it in scsi low-level (HBA) driver ?
You can use vmalloc in any situation where you are in task context and can sleep.
> I am currently using the new error handling code. (use_new_eh_code = TRUE).
Then yes you would need to drop the lock if my memory serves me rightly. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |