All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andi Kleen <ak@muc.de>,
	Joe Thornber <joe@fib011235813.fsnet.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Device-mapper submission 6/7
Date: Fri, 18 Oct 2002 02:48:45 +0200	[thread overview]
Message-ID: <20021018004844.GA14275@averell> (raw)
In-Reply-To: <3DAED2DB.3030407@pobox.com>

> ioctls are analogous to procfs:  they are simple, easy, and usually the 
> wrong thing to do.

Simple truths. Like always you need to add your common sense though.

I just contend that it's not always the right thing to try to clamp
what's a simple ioctl into a complicated file system. From Joe's description
of the fs interface it sounds to me like the ioctls are a lot simpler
than the fs based version. KISS principle applies.

-Andi

  reply	other threads:[~2002-10-18  0:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 17:58 [PATCH] Device-mapper submission 6/7 Joe Thornber
2002-10-15 18:15 ` Jeff Garzik
2002-10-15 18:59   ` Greg KH
2002-10-15 21:44   ` Joe Thornber
2002-10-16 14:20     ` Jeff Garzik
2002-10-16 14:38       ` Anton Blanchard
2002-10-16 15:20         ` Jeff Garzik
2002-10-16 15:20       ` Joe Thornber
2002-10-16 15:59         ` Jeff Garzik
2002-10-17  8:05           ` Joe Thornber
2002-10-17  8:26             ` Andi Kleen
2002-10-17  8:50               ` Joe Thornber
2002-10-17 16:54                 ` Jeff Garzik
2002-10-18 11:38                   ` Jakob Oestergaard
2002-10-17 15:10               ` Jeff Garzik
2002-10-18  0:48                 ` Andi Kleen [this message]
2002-10-17  0:46         ` Greg KH

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=20021018004844.GA14275@averell \
    --to=ak@muc.de \
    --cc=jgarzik@pobox.com \
    --cc=joe@fib011235813.fsnet.co.uk \
    --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 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.