From: Adrian Bunk <bunk@fs.tum.de>
To: neilb@cse.unsw.edu.au
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
davem@redhat.com, sparclinux@vger.kernel.org, ak@suse.de,
discuss@x86-64.org, gniibe@m17n.org, kkojima@rr.iij4u.or.jp,
linux-sh@m17n.org
Subject: modular nfsd requires kernel changes on sh, sparc64, x86_64
Date: Sat, 13 Mar 2004 18:34:44 +0100 [thread overview]
Message-ID: <20040313173444.GX14833@fs.tum.de> (raw)
Compiling and inserting a module into the currently running kernel
should work without needing a reboot.
For nfsd this seems to work everywhere except on the sh, sparc64
and x86_64 architectures where adding the nfsd module changes
non-modular kernel code (checked in 2.6.4-mm1):
arch/sh/kernel/entry.S:
<-- snip -->
...
#if !defined(CONFIG_NFSD) && !defined(CONFIG_NFSD_MODULE)
#define sys_nfsservctl sys_ni_syscall
#endif
...
<-- snip -->
arch/x86_64/ia32/sys_ia32.c:
<-- snip -->
...
#if defined(CONFIG_NFSD) || defined(CONFIG_NFSD_MODULE)
/* Stuff for NFS server syscalls... */
struct nfsctl_svc32 {
u16 svc32_port;
s32 svc32_nthreads;
};
struct nfsctl_client32 {
...
<-- snip -->
arch/sparc64/kernel/sys_sparc32.c:
<-- snip -->
...
#if defined(CONFIG_NFSD) || defined(CONFIG_NFSD_MODULE)
/* Stuff for NFS server syscalls... */
struct nfsctl_svc32 {
u16 svc32_port;
s32 svc32_nthreads;
};
struct nfsctl_client32 {
...
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2004-03-13 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 17:34 Adrian Bunk [this message]
2004-03-13 18:05 ` Andi Kleen
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=20040313173444.GX14833@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=discuss@x86-64.org \
--cc=gniibe@m17n.org \
--cc=kkojima@rr.iij4u.or.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@m17n.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=sparclinux@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
all inboxes | Powered by JetHome®