public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, dalecki@evision-ventures.com
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][CFT] IDE TCQ #2
Date: Tue, 9 Apr 2002 16:38:41 GMT	[thread overview]
Message-ID: <UTC200204091638.QAA519161.aeb@cwi.nl> (raw)

    > In my opinion sysctl() is worthless. It uses an array of numbers
    > where ioctl() uses a single number. Especially since the names are
    > already in the kernel it is much clearer and cleaner to use a
    > pathname. I wouldn't mind if sysctl() disappeared entirely.

    Please have a look at /proc/sys/ OK?

    > Also ioctl() has its problems. First of all, nobody knows what the
    > prototype is. Secondly, it is too rigid - the moment one needs a
    > larger structure one needs a different ioctl.
    > 
    > A text based interface is much more flexible. If the number of
    > cylinders of a disk no longer fits in a short, well doesn't matter,
    > then the number of digits may increase but the interface remains
    > unchanged. Of course the price is that one has to parse, but
    > typically that is not a problem.

What do you want me to see in /proc/sys/?
Pathnames? That is what I like.
I dislike the system call, with its ugly numbers.

Andries


             reply	other threads:[~2002-04-09 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 16:38 Andries.Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-09 15:34 [PATCH][CFT] IDE TCQ #2 Andries.Brouwer
2002-04-09 15:22 ` Martin Dalecki
2002-04-09 12:44 Jens Axboe
2002-04-09 12:24 ` Martin Dalecki
2002-04-09 13:41   ` Jens Axboe
2002-04-10  8:55 ` Martin Dalecki
2002-04-10  9:58   ` Jens Axboe
2002-04-10  9:04     ` Martin Dalecki
2002-04-10 10:09       ` Jens Axboe
2002-04-10  9:12         ` Martin Dalecki

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=UTC200204091638.QAA519161.aeb@cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=axboe@suse.de \
    --cc=dalecki@evision-ventures.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