linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Rahul Theraja" <rahul.theraja@gmail.com>
To: "Shakthi Kannan" <shakthimaan@gmail.com>
Cc: kernelnewbies@nl.linux.org, linuxppc-embedded@ozlabs.org
Subject: Re: help in block drivers
Date: Thu, 19 Oct 2006 21:53:24 +0530	[thread overview]
Message-ID: <ff9652ca0610190923vffbb981j1978ce4159489b0c@mail.gmail.com> (raw)
In-Reply-To: <d16b1c80610190808y17c516dl35cfc8ca4a7a42ad@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

Hello Shakthi Kannan,

Thanks for the reply .

> driver. I could not understand why the "sbd_request " is called even
> though
> > i have given only one read call from user space file.
>
> Block device I/O transfer is done in blocks.
>
> >  And also in the driver, in the function sbd_request() how does the
> driver
> > get the parameters  like sector, current_nr_sectors and buffer.
>
> VFS <-> SCSI <-> Block device?
>
> > i could move
> > furhter fastly.
>
> Fastly? IMHO, learning kernel development involves lot of patience.
>
> SK



Is it necessary to use kernel_thread() in block drivers. In  drivers/block
loop.c i could see  kernel_thread() being used but in floopy.c it is not
used. When is this kernel_thread() function is supposed to be used ?  In the
sbd_device also the kernel_thread() is not used.

Anyone please kindly clarify my doubts.

Thanks in Advance

-Rahul

[-- Attachment #2: Type: text/html, Size: 1237 bytes --]

       reply	other threads:[~2006-10-19 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ff9652ca0610190314u32a620b5qd0bd27a1b2700a22@mail.gmail.com>
     [not found] ` <d16b1c80610190808y17c516dl35cfc8ca4a7a42ad@mail.gmail.com>
2006-10-19 16:23   ` Rahul Theraja [this message]
2006-10-20  5:13     ` help in block drivers Fawad Lateef
2006-10-22  9:02       ` Rahul
2006-10-24  9:37         ` Rahul
2006-10-24 12:14           ` Fawad Lateef

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=ff9652ca0610190923vffbb981j1978ce4159489b0c@mail.gmail.com \
    --to=rahul.theraja@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=shakthimaan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).