* Re: [PATCH] cifs: document 'fsc' mount option
[not found] ` <AANLkTi=+Y1XdFCT1UfWZW==qusXfs6t-vxa_CYo03TTT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2010-07-27 21:59 ` Randy Dunlap
2010-07-30 9:49 ` Suresh Jayaraman
1 sibling, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2010-07-27 21:59 UTC (permalink / raw)
To: Steve French
Cc: Suresh Jayaraman, Jeff Layton, linux-cifs-u79uwXL29TY76Z2rM5mHXA,
linux-fsdevel
On Tue, 27 Jul 2010 11:38:20 -0500 Steve French wrote:
> On Tue, Jul 27, 2010 at 11:33 AM, Suresh Jayaraman <sjayaraman@suse.de> wrote:
> > On 07/27/2010 08:51 PM, Steve French wrote:
> >> scripts/extract-ikconfig could be run against the image (or look at
> >> /proc/config.gz) - but unless there is an easier way to view kernel
> >> config options on particular distros via distro specific tools -
> >> probably easier just to note that CONFIG_FSCACHE must be selected in
> >> the kernel build (since it forces dependencies on the other kernel
> >> options being set)
> >
> > Does something like
> > $zcat /proc/config.gz | grep CONFIG_CIFS_FSCACHE
> >
> > might work on all distros?
> >
> > But, Jeff's idea of having a features file in /proc sounds good. Apart
> > from using them as a reference to check in documentation, it could be a
> > useful information while collecting debugging output as well..?
>
> Seems reasonable - but wondering if other file systems have run into the same
> problem - how to view their build/config options - and how they have
> solved it (if at all) so ccing fsdevel
There is no guarantee that scripts/extract-ikconfig can find anything,
or that proc/config.gz is present.
The safe, sure-to-work thing to do is create some strings or files or whatever
based on CONFIG_* kconfig symbols during kernel build, then those hints will
be available at kernel run-time.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH] cifs: document 'fsc' mount option
[not found] ` <AANLkTi=+Y1XdFCT1UfWZW==qusXfs6t-vxa_CYo03TTT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-27 21:59 ` Randy Dunlap
@ 2010-07-30 9:49 ` Suresh Jayaraman
1 sibling, 0 replies; 3+ messages in thread
From: Suresh Jayaraman @ 2010-07-30 9:49 UTC (permalink / raw)
To: Steve French
Cc: Jeff Layton, linux-cifs-u79uwXL29TY76Z2rM5mHXA, linux-fsdevel
On 07/27/2010 10:08 PM, Steve French wrote:
> On Tue, Jul 27, 2010 at 11:33 AM, Suresh Jayaraman <sjayaraman@suse.de> wrote:
>> On 07/27/2010 08:51 PM, Steve French wrote:
>>> scripts/extract-ikconfig could be run against the image (or look at
>>> /proc/config.gz) - but unless there is an easier way to view kernel
>>> config options on particular distros via distro specific tools -
>>> probably easier just to note that CONFIG_FSCACHE must be selected in
>>> the kernel build (since it forces dependencies on the other kernel
>>> options being set)
>>
>> Does something like
>> � � � �$zcat /proc/config.gz | grep CONFIG_CIFS_FSCACHE
>>
>> might work on all distros?
>>
>> But, Jeff's idea of having a features file in /proc sounds good. Apart
>> from using them as a reference to check in documentation, it could be a
>> useful information while collecting debugging output as well..?
>
> Seems reasonable - but wondering if other file systems have run into the same
> problem - how to view their build/config options - and how they have
> solved it (if at all) so ccing fsdevel
>
I just checked some of the other filesystems. Most of them just mention
the CONFIG_XXX option has to be set/enabled.
For e.g.
(1) Mount options for jfs
iocharset=name
...
This requires CONFIG_NLS_UTF8 to be set in the kernel .config
file.
(2) Mount options for tmpfs
mpol=[default|prefer:Node|bind:NodeList|interleave|interleave:NodeList]
Set the NUMA memory allocation policy for all files in that
instance (if the kernel CONFIG_NUMA is enabled) ...
Thanks,
--
Suresh Jayaraman
^ permalink raw reply [flat|nested] 3+ messages in thread