Re: asynchronous request procesisng in ram based block dev driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 2, 2009 at 8:46 AM, Lal <learner.kernel@xxxxxxxxx> wrote:
> On Tue, Mar 31, 2009 at 2:03 PM, nidhi mittal <nidhimittal19@xxxxxxxxx> wrote:
>> hi
>> i have written a very simple ram based block device driver
>> processing request asynchronously
>>
>> wherein
>> in request function -- dequeue the req from req queue and add it to the
>> linked list
>> then in the function triggered by timer
>> handle each req from the linked list
>> then blk_end_requets is called upon completion of request .
>>
>>
>
>>                 blkdev_dequeue_request(req);
>>                 my_req = (struct filtered_request*)kzalloc(sizeof(struct
>> filtered_request),GFP_KERNEL);
>
> In request function, you should use GFP_ATOMIC
>

this is new to me, can i know why it should be GFP_ATOMIC?


-- 
Regards,
Peter Teoh

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux