public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: davidm@hpl.hp.com
Cc: Andrew Morton <akpm@osdl.org>,
	Jes Sorensen <jes@trained-monkey.org>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [patch] 2.6.1-mm5 compile do not use shared extable code for
Date: Tue, 27 Jan 2004 23:49:10 +0000	[thread overview]
Message-ID: <16406.63734.400759.452955@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <16406.36741.510353.456578@napali.hpl.hp.com>

David Mosberger writes:

>   Paul> Also, I don't think there is enough code there to be worth the
>   Paul> bother of trying to abstract the generic routine so you can
>   Paul> plug in different compare and move-element routines.  The
>   Paul> whole sort routine is only 16 lines of code, after all.  Why
>   Paul> not just have an ia64-specific version of sort_extable?
>   Paul> That's what I thought you would do.
> 
> Because the Alpha needs exactly the same code.

I really don't like the uglification of lib/extable.c.  I think it is
much better to have ~20 lines of code in each of arch/ia64/mm and
arch/alpha/mm than to try to generalize lib/extable.c.  Once you add
all the extra definitions you need for your version, I doubt that the
overall savings would be more than a dozen lines or so.

The point is that with lib/extable.c as it is, you can look at one
page of code, and everything you need to understand that code is
there.  With your change, I have to hunt around to check what the
macros are doing on each arch, and flip backwards and forwards to
check side effects, calling environment etc.  With an ia64-specific
extable.c, you should be able to look at one page of code there and
see that the ia64 version is also correct.

Paul.

  reply	other threads:[~2004-01-27 23:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20 12:23 [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 Jes Sorensen
2004-01-20 17:00 ` [patch] 2.6.1-mm5 compile do not use shared extable code for Andrew Morton
2004-01-24  3:00   ` David Mosberger
2004-01-24 10:49     ` Paul Mackerras
2004-01-26 23:33       ` David Mosberger
2004-01-27  8:11         ` [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 Jes Sorensen
2004-01-27 17:39           ` David Mosberger
2004-01-27  8:56         ` [patch] 2.6.1-mm5 compile do not use shared extable code for Paul Mackerras
2004-01-27 16:19           ` David Mosberger
2004-01-27 23:49             ` Paul Mackerras [this message]
2004-01-28  6:06               ` David Mosberger
2004-01-27 17:54           ` David Mosberger
2004-01-21 18:43 ` [patch] 2.6.1-mm5 compile do not use shared extable code for ia64 David Mosberger

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=16406.63734.400759.452955@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=akpm@osdl.org \
    --cc=davidm@hpl.hp.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-ia64@vger.kernel.org \
    --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