From: Christoph Hellwig <hch@infradead.org>
To: Dean Nelson <dcn@sgi.com>
Cc: linux-ia64@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH 2/4] SGI Altix cross partition functionality (1st revision)
Date: Tue, 24 Aug 2004 20:17:33 +0100 [thread overview]
Message-ID: <20040824201733.B32110@infradead.org> (raw)
In-Reply-To: <20040824182344.GB13961@sgi.com>; from dcn@sgi.com on Tue, Aug 24, 2004 at 01:23:44PM -0500
On Tue, Aug 24, 2004 at 01:23:44PM -0500, Dean Nelson wrote:
> This patch contains the shim module (XP) which interfaces between the
> communication module (XPC) and the functional support modules (like XPNET).
>
> Signed-off-by: Dean Nelson <dcn@sgi.com>
>
>
> Index: linux/arch/ia64/Kconfig
> ===================================================================
> --- linux.orig/arch/ia64/Kconfig 2004-08-17 13:31:26.000000000 -0500
> +++ linux/arch/ia64/Kconfig 2004-08-23 11:39:50.000000000 -0500
> @@ -189,6 +189,16 @@
> depends on !IA64_HP_SIM
> default y
>
> +config IA64_SGI_SN_XPC
> + tristate "Support DMA Messaging between SGI machines"
Why do you have three different option when the only way they're usefull
is to have all three enabled at the same time. Also as I mentioned previously
please merge at least xp and xpc into a single module.
> + depends on FETCHOP
Please make sure the fetchop driver is at least posted publically
before submitting anything that depends on it.
> +xp-y := xp_main.o xp_kdb.o xp_nofault.o
Please kill all the kdb hooks for mainline submission.
> + case xpcMsgReceived: return "xpcMsgReceived";
> + case xpcMsgDelivered: return "xpcMsgDelivered";
Please don't add strerror-lookalikes to the kernel.
> + for (ch_number = 0; ch_number < XPC_NCHANNELS; ch_number++) {
> + sema_init(&xpc_registrations[ch_number].sema, 1); /* mutex */
> + }
A single mutex wouldn't do it? It doesn't exactly look like it's used in
fast-paths
> + */
> + if ((ret = sn_register_nofault_code(*(u64 *) pior_func,
> + *(u64 *) pior_err_func,
> + *(u64 *) pior_err_func, 1, 1)) != 0) {
Is the strange casting really unavoidable?
next prev parent reply other threads:[~2004-08-24 19:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 18:00 [PATCH 0/4] SGI Altix cross partition functionality (1st revision) Dean Nelson
2004-08-24 18:22 ` [PATCH 1/4] " Dean Nelson
2004-08-24 19:13 ` Christoph Hellwig
2004-08-24 18:23 ` [PATCH 2/4] " Dean Nelson
2004-08-24 19:17 ` Christoph Hellwig [this message]
2004-08-24 18:26 ` [PATCH 3/4] " Dean Nelson
2004-08-24 18:27 ` [PATCH 4/4] " Dean Nelson
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=20040824201733.B32110@infradead.org \
--to=hch@infradead.org \
--cc=dcn@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).