From: Andi Kleen <andi@firstfloor.org>
To: jassi brar <jassi_singh_brar@yahoo.com>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>
Subject: Re: An idea .... with code
Date: Wed, 27 Aug 2008 09:47:51 +0200 [thread overview]
Message-ID: <20080827074751.GO26610@one.firstfloor.org> (raw)
In-Reply-To: <348573.4171.qm@web33204.mail.mud.yahoo.com>
On Wed, Aug 27, 2008 at 12:24:07AM -0700, jassi brar wrote:
> Exceptions(special cases) make for entropy and hence complexity. Generalization keeps uniformity and hences Order and Ease.
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.
> I am not for discarding features from the system, but for implementing them in a way that is lesser intrusive.
But you're adding more code which is more intrusive?
> > Can you please expand a bit why you think losetup is that complicated
> > and what the problem is with it?
> Sir, i don't object to losetup as such. It is a utility made(specifically?) for LOOP devices: which implements unnecessary gears and switches to operate.
> I object only to what could be done without using ioctls and not to features that losetup provides for devices other than Loop(are there any?)
Your goal is to replace all ioctls with sysfs files?
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.
-Andi
next prev parent reply other threads:[~2008-08-27 7:45 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 [this message]
2008-08-27 9:57 ` David Newall
2008-08-27 10:01 ` Andi Kleen
2008-08-27 12:38 ` jassi brar
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=20080827074751.GO26610@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=jassi_singh_brar@yahoo.com \
--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