public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: bitops.h ifdef __KERNEL__ cleanup.
Date: Thu, 19 Jul 2001 12:54:43 MET-1	[thread overview]
Message-ID: <911753F4952@vcnet.vc.cvut.cz> (raw)

On 18 Jul 01 at 23:54, David Woodhouse wrote:

> Not all architectures put clear_bit et al in asm/bitops.h in a form which 
> is usable from userspace. Yet because it happens to work on a PeeCee, 
> people do it anyway. 

Please do not do this. At least ncpfs checks for usability of these
ops from its configure script, and if they are not available/usable, 
it reverts to pthread mutex based implementation, which is slower 
dozen of times. Same applies for atomic_* functions.

I think that you should complain to userspace authors who do not
check for bitops existence and not force other to distrbute 8+ versions
of bitops.h with their application, together with infrastructure for
selecting correct version...

Just my 0.02c.
                                            Petr Vandrovec
                                            vandrove@vc.cvut.cz

             reply	other threads:[~2001-07-19 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19 12:54 Petr Vandrovec [this message]
2001-07-19 11:48 ` bitops.h ifdef __KERNEL__ cleanup Russell King
  -- strict thread matches above, loose matches on Subject: below --
2001-07-19 19:21 Petr Vandrovec
2001-07-19 18:37 ` Russell King
2001-07-19 21:53 ` David Woodhouse
2001-07-20  4:18   ` H. Peter Anvin
2001-07-21  6:41     ` Jeff Garzik
2001-07-27  5:05       ` Eric W. Biederman
2001-07-18 22:54 David Woodhouse

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=911753F4952@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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