linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@lazybastard.org>
To: Greg KH <greg@kroah.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@osdl.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
	David Chinner <dgc@sgi.com>
Subject: Re: [PATCH 1/2] LogFS proper
Date: Wed, 9 May 2007 12:24:24 +0200	[thread overview]
Message-ID: <20070509102424.GB29978@lazybastard.org> (raw)
In-Reply-To: <20070509000101.GB3967@kroah.com>

On Tue, 8 May 2007 17:01:01 -0700, Greg KH wrote:
> On Wed, May 09, 2007 at 01:10:09AM +0200, J??rn Engel wrote:
> > 
> > The remaining question is how to deal with kernel-only code that uses
> > be64.  Convert that to __be64 as well?  Or introduce be64 in
> > include/linix/types.h instead?
> 
> I say leave it alone for now, it's not that common :)

Using a fairly lame grep, there are 10k instances versus 60k for u64 and
friends.  Sustract about 2.5k used in include/ and possibly part of
userspace interfaces, that leaves about 7.5k.

joern@Galway:/usr/src/kernel/logfs$ sgrep '\<u[136][246]\>' .|wc
  60306  313780 3960665
joern@Galway:/usr/src/kernel/logfs$ sgrep '\<__[lb]e[136][246]\>' .|wc
  10013   52235  635047
joern@Galway:/usr/src/kernel/logfs$ sgrep '\<__[lb]e[136][246]\>' include|wc
   2624   15100  173176

Actually going through them all, the overwhelming majority is used for
structures.  I seem to be quite the oddball indeed.

Will change.

Jörn

-- 
The grand essentials of happiness are: something to do, something to
love, and something to hope for.
-- Allan K. Chalmers
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-05-09 10:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 21:59 [PATCH 0/2] LogFS take two Jörn Engel
2007-05-07 22:00 ` [PATCH 1/2] LogFS proper Jörn Engel
2007-05-07 22:10   ` Jörn Engel
2007-05-07 22:11   ` Jörn Engel
2007-05-08  7:22   ` Thomas Gleixner
2007-05-08 12:46     ` Jan Engelhardt
2007-05-08 15:54       ` Thomas Gleixner
2007-05-08 16:17         ` Evgeniy Polyakov
2007-05-09 13:06           ` Jan Engelhardt
2007-05-08 16:32     ` Jörn Engel
2007-05-08 18:00       ` Thomas Gleixner
2007-05-08 20:25         ` Jörn Engel
2007-05-08 20:58           ` Thomas Gleixner
2007-05-08 21:30             ` Jörn Engel
2007-05-08 19:15       ` Pekka Enberg
2007-05-08 20:58         ` Jörn Engel
2007-05-08 22:52           ` Greg KH
2007-05-08 23:10             ` Jörn Engel
2007-05-09  0:01               ` Greg KH
2007-05-09 10:24                 ` Jörn Engel [this message]
2007-05-08 22:44     ` Ingo Oeser
2007-05-08 23:05       ` Jörn Engel
2007-05-07 22:01 ` [PATCH 2/2] introduce I_SYNC Jörn Engel
2007-05-08  7:23   ` Thomas Gleixner
2007-05-08 12:00     ` Jörn Engel
2007-05-08  7:39 ` [PATCH 0/2] LogFS take two Thomas Gleixner
2007-05-08 11:41   ` Jörn Engel

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=20070509102424.GB29978@lazybastard.org \
    --to=joern@lazybastard.org \
    --cc=akpm@osdl.org \
    --cc=dgc@sgi.com \
    --cc=greg@kroah.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=shaggy@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).