public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jassi brar <jassi_singh_brar@yahoo.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: An idea .... with code
Date: Wed, 27 Aug 2008 05:38:48 -0700 (PDT)	[thread overview]
Message-ID: <35042.98883.qm@web33207.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080827074751.GO26610@one.firstfloor.org>

--- On Wed, 8/27/08, Andi Kleen <andi@firstfloor.org> wrote:

> I fail to see what your patch generalizes? AFAIK it just
> adds a new
> more narrow (less features than the old one) interface to
> create loop devices.
 Btw, my code is not a patch to the loop driver, its an altogether new module. May i daresay, it aims squarely at drivers/block/loop.c and mean to replace it altogether.
 My module generalizes in the way that it doesn't add or make use of any ioctl. It doesn't even export a variable and makes uses only of what other subsystems provide for(block, sysfs, vfs).
 As far as features are concerned, please suggest me what could be done with /dev/loop0 and not for /dev/vblk?


> But you're adding more code which is more intrusive? 
 To be exact, i mean to _replace_ driver/block/loop.c, and hence _remove_ all the loop specific ioctls and max# limitations, with drivers/block/vblk.c :D



> Your goal is to replace all ioctls with sysfs files? 

  Please do have a look at the code.

 I add only one sysfs interface (manage), which when read returns the status of all the files being emulated and when written updates(add/remove) emulation of a file.
 The interface could be made more useful by echo'ing in other parameters along with filename for example:
echo +[r/w]+[sects]+[cyls]+[heads]+[filename] > /sys/devices/virblk/manage
 for specifyinf readonly, cylinders, heads, sectsize for the file to be emulated.


> If it's that then I'm going on the book as saying
> that's a bad idea, especially
> for this case. While ioctls have their problems they work
> quite well for many 
> things. I don't see any particular reason why ioctls
> should not be used
> to configure loop devices.
  I don't intend to revolt against the concept of ioctls. Being an embedded linux engineer I do understand the importance of ioctls: i declare one every other day for configuring custom h/w: Graphics and Multimedia esp so.
 As for loop devices, i think we can make do without'em.

Regards,
-Jassi


      

  parent reply	other threads:[~2008-08-27 12:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24  8:53 An idea .... with code jassi brar
2008-08-25 12:22 ` Jochen Voß
2008-08-25 20:53   ` Marcin Slusarz
2008-08-26  2:47 ` Bill Davidsen
2008-08-26  8:24 ` Andi Kleen
2008-08-26 10:44   ` Alexey Dobriyan
2008-08-26 11:08     ` Andi Kleen
2008-08-27  7:24   ` jassi brar
2008-08-27  7:47     ` Andi Kleen
2008-08-27  9:57       ` David Newall
2008-08-27 10:01         ` Andi Kleen
2008-08-27 12:38       ` jassi brar [this message]
2008-08-27 12:47         ` Andi Kleen
2008-08-27 14:49           ` Kasper Sandberg
2008-08-27 15:02             ` Andi Kleen
2008-08-28  1:24               ` jassi brar
2008-08-28  9:41               ` Kasper Sandberg
2008-08-30  2:57             ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2008-08-27  0:44 jassi brar
2008-08-27  2:27 jassi brar

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=35042.98883.qm@web33207.mail.mud.yahoo.com \
    --to=jassi_singh_brar@yahoo.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox