All of lore.kernel.org
 help / color / mirror / Atom feed
From: mandeepsandhu.chd@gmail.com (Mandeep Sandhu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: interview question how does application connects to device
Date: Wed, 6 Jul 2011 10:42:27 +0530	[thread overview]
Message-ID: <CAC+QLdTCkzY5aRDuUF7Vg8JHP0pFc-p+RoHGcrTHuWa1N5xK8w@mail.gmail.com> (raw)
In-Reply-To: <769A0B32-0869-4A2B-A005-D6AC0376D1E3@gmail.com>

> How would using sysfs be useful if we were to talk about interacting with, let's say, a file system? ioctl's are quite versatile and rather easy to use when one wants to interact with a given FS.
>
> For instance, one can manage a Btrfs file system by using an user-level tool, which heavily uses ioctl's. Requiring it to interact with sysfs instead seems like complicating something simple with no apparent purpose.

Franlky, I've never used the sysfs interface and mostly know it from
'theoretical' view-point. It was created mostly for providing a
uniform way for user-space applications (udev/HAL, driver tools, etc)
to interact with a device driver. It exposes the underlying device
topology as a directory tree.

I'm not sure how sysfs applies to 'filesystem' as it depicts a
particular 'device hierarchy tree' within a kernel. As Greg mentioned
here, lot filesystem drivers still prefer to use the ioctl interface.
However, one use for it which I can see, is for controlling the
underlying block device (hard-disk, USB mass storage etc).

HTH,
-mandeep

  parent reply	other threads:[~2011-07-06  5:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOQuo6Nf9-uXBbHOi1_tpBmBOVPzuBtW699=ywDGSsfT_NVphA@mail.gmail.com>
2011-07-05  4:15 ` interview question how does application connects to device Bond
2011-07-05  5:43   ` Prashant Shah
2011-07-17 15:10     ` Bond
2011-07-17 15:34       ` Anuz Pratap Singh Tomar
2011-07-17 15:40         ` Bond
2011-07-17 15:47           ` Anuz Pratap Singh Tomar
2011-07-17 15:52             ` Bond
2011-07-17 16:06               ` Mulyadi Santosa
2011-07-17 17:34                 ` Bond
2011-07-17 17:49                   ` Anuz Pratap Singh Tomar
2011-07-17 19:25                   ` Greg Freemyer
2011-07-17 16:14               ` Anuz Pratap Singh Tomar
2011-07-17 17:31                 ` Bond
2011-07-05  6:51   ` Philipp Ittershagen
2011-07-05  6:59     ` Paraneetharan Chandrasekaran
2011-07-05  7:28       ` Mandeep Sandhu
2011-07-05  7:31         ` Mandeep Sandhu
2011-07-05  7:51           ` Abhijit Pawar
2011-07-05  8:12             ` er krishna
2011-07-05  9:13               ` Mandeep Sandhu
2011-07-05  9:38                 ` er krishna
2011-07-05 12:56   ` Greg Freemyer
2011-07-05 13:43     ` Mandeep Sandhu
2011-07-05 16:03       ` Greg Freemyer
2011-07-06  4:08         ` Abhijit Pawar
2011-07-06  4:43           ` Prashant Shah
2011-07-06  5:27             ` Abhijit Pawar
2011-07-11 17:43         ` StephanT
2011-07-11 18:13           ` Greg KH
2011-07-11 18:14           ` Greg Freemyer
     [not found]       ` <769A0B32-0869-4A2B-A005-D6AC0376D1E3@gmail.com>
2011-07-06  5:12         ` Mandeep Sandhu [this message]
2011-07-06 23:29           ` Javier Martinez Canillas
2011-07-07  3:20             ` Greg Freemyer
2011-07-07 12:51               ` Javier Martinez Canillas
2011-07-05 13:36   ` Shaz

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=CAC+QLdTCkzY5aRDuUF7Vg8JHP0pFc-p+RoHGcrTHuWa1N5xK8w@mail.gmail.com \
    --to=mandeepsandhu.chd@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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.