From: Benny Halevy <bhalevy@panasas.com>
To: Fred Isaman <iisaman@netapp.com>
Cc: Jim Rees <rees@umich.edu>, Steve Dickson <SteveD@redhat.com>,
Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
peter honeyman <honey@citi.umich.edu>
Subject: Re: Updated pNFS Developmental kernel repository
Date: Fri, 01 Oct 2010 22:59:47 +0200 [thread overview]
Message-ID: <4CA64BC3.8040404@panasas.com> (raw)
In-Reply-To: <AANLkTin9+_aWyLMv1xP9ou1YRXfY46dgK7J-to+p5LTb@mail.gmail.com>
On 2010-10-01 22:13, Fred Isaman wrote:
> On Fri, Oct 1, 2010 at 4:07 PM, Jim Rees <rees@umich.edu> wrote:
>> Steve Dickson wrote:
>>
>> On 10/01/2010 09:51 AM, Tigran Mkrtchyan wrote:
>> >
>> > Hi Steve,
>> >
>> > thanks for the builds. What I am missing is modprobe configuration file
>> > which I have to add myself.
>> Unfortunately yes... I have not figured out a good way to have
>> the mobprobe done on the client since, in general, init scripts
>> don't run on the client (with the exception of rpc.statd and rpc.gssd).
>>
>> I guess I could come up with an pnfs init script..but that
>> seems like a bit overkill just to do a modprobe...
>>
>> I've already got an init script for the block layout client that does the
>> modprobe and starts the daemon. How about we generalize it to modprobe the
>> other modules too, and call it the pnfs init script?
>
> The current code is designed to request the loading of the module as
> needed. All that is needed is an alias, of the type
>
> alias nfs-layouttype4-[INTEGER_ID] ACTUAL_MODULE_NAME
I think that's too complicated.
Why not export a well known symbol from the layout driver,
encoding the layout type, to be looked up by the kernel?
Benny
>
> Fred
>
>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-01 20:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 11:04 Updated pNFS Developmental kernel repository Steve Dickson
[not found] ` <4CA5C059.6000805-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-10-01 11:18 ` Tigran Mkrtchyan
2010-10-01 13:51 ` Tigran Mkrtchyan
2010-10-01 19:57 ` Steve Dickson
2010-10-01 20:05 ` Fred Isaman
2010-10-01 20:07 ` Jim Rees
2010-10-01 20:13 ` Fred Isaman
2010-10-01 20:59 ` Benny Halevy [this message]
2010-10-01 20:58 ` Benny Halevy
2010-10-02 12:45 ` Tigran Mkrtchyan
2010-10-02 16:49 ` Steve Dickson
2010-10-01 12:56 ` Jim Rees
-- strict thread matches above, loose matches on Subject: below --
2010-09-01 16:06 Steve Dickson
2010-08-24 22:12 Steve Dickson
2010-07-02 5:30 Steve Dickson
2010-06-02 12:00 Steve Dickson
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=4CA64BC3.8040404@panasas.com \
--to=bhalevy@panasas.com \
--cc=SteveD@redhat.com \
--cc=honey@citi.umich.edu \
--cc=iisaman@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=tigran.mkrtchyan@desy.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).