linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel
	<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] cifs: document 'fsc' mount option
Date: Fri, 30 Jul 2010 15:19:14 +0530	[thread overview]
Message-ID: <4C52A01A.4090408@suse.de> (raw)
In-Reply-To: <AANLkTi=+Y1XdFCT1UfWZW==qusXfs6t-vxa_CYo03TTT-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

      parent reply	other threads:[~2010-07-30  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4C4EE408.7070109@suse.de>
     [not found] ` <20100727103313.4b730ea8@tlielax.poochiereds.net>
     [not found]   ` <AANLkTina2EyHkrgNAcrY8ZRK=fXQS71dekWc+kOA0+mz@mail.gmail.com>
     [not found]     ` <20100727111517.4fe0859e@tlielax.poochiereds.net>
     [not found]       ` <AANLkTik9JqtqAtKJQsaQR8aC8s0kwmrcU=_=QQei7U07@mail.gmail.com>
     [not found]         ` <4C4F0A71.8020908@suse.de>
2010-07-27 16:38           ` [PATCH] cifs: document 'fsc' mount option Steve French
     [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 [this message]

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=4C52A01A.4090408@suse.de \
    --to=sjayaraman-l3a5bk7wagm@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).