All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ron Croonenberg <ronc@lanl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] lustre kernel configuration
Date: Tue, 21 May 2013 13:36:40 -0600	[thread overview]
Message-ID: <519BCCC8.70506@lanl.gov> (raw)
In-Reply-To: <CDC13365.C781%spitzcor@cray.com>

ok, cool thanks..   that probably will work better. (there were still a 
bunch of config options that were 'NEW' but a lot less

Ron

On 05/21/2013 01:24 PM, Cory Spitz wrote:
> Kernel configs are kept in the tree.  You can find master's set at
> http://git.whamcloud.com/?p=fs/lustre-release.git;a=tree;f=lustre/kernel_pa
> tches/kernel_configs;h=88ca1484fa6597a7d786f3f09f03612f6d039db2;hb=HEAD
>
> -Cory
>
> On 5/21/13 2:04 PM, "Ron Croonenberg" <ronc@lanl.gov> wrote:
>
>> Hi Chris,
>>
>> thanks for the link.  What I was looking for was the Linux kernel config
>> but couldn't find any documentation foor (would have been nice to find
>> the ones that are actuallu used in the binaries).
>>
>> Basically what I did is take my RHEL6 config and configured the kernel
>> wit and compiling that seemed to work. (I did compile the rpms, just a
>> regular make. That seemed to work for 1.8.7.
>> I haven't installed anything yet., so we'll see on that part.
>>
>> thanks,
>>
>> Ron
>>
>> On 05/21/2013 12:16 PM, Christopher J. Morrone wrote:
>>> If you use the zfs osd for your servers, there is no need to modify your
>>> Linux kernel.  That is probably a much easier way to get started with
>>> Lustre development.
>>>
>>> If you are set on using the ldiskfs osd, Intel has some instructions on
>>> their wiki here:
>>>
>>>      https://wiki.hpdd.intel.com/display/PUB/Building+Lustre+from+Source
>>>
>>> Chris
>>>
>>> On 05/21/2013 07:11 AM, Ron Croonenberg wrote:
>>>> hello,
>>>>
>>>> I am looking into some Lustre development but want to build everything
>>>> from scratch. I looked around to see how the linux kernel is configured
>>>> but don't seem to find anything.
>>>>
>>>> any ideas?
>>>>
>>>> thanks,
>>>>
>>>> Ron
>>>> _______________________________________________
>>>> Lustre-devel mailing list
>>>> Lustre-devel at lists.lustre.org
>>>> http://lists.lustre.org/mailman/listinfo/lustre-devel
>>>>
>>>
>>> _______________________________________________
>>> Lustre-devel mailing list
>>> Lustre-devel at lists.lustre.org
>>> http://lists.lustre.org/mailman/listinfo/lustre-devel
>>>
>> _______________________________________________
>> Lustre-devel mailing list
>> Lustre-devel at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-devel
>

  reply	other threads:[~2013-05-21 19:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 22:03 [Lustre-devel] Interested in contributing to Lustre twanjari at andrew.cmu.edu
2013-05-13 21:34 ` Prakash Surya
2013-05-14  6:49   ` Drokin, Oleg
2013-05-14 14:58     ` Cory Spitz
2013-05-14 15:23       ` Nikitas Angelinas
2013-05-21 14:08     ` [Lustre-devel] building the 'lustre kernel' Ron Croonenberg
2013-05-21 14:11     ` [Lustre-devel] lustre kernel configuration Ron Croonenberg
2013-05-21 18:16       ` Christopher J. Morrone
2013-05-21 19:04         ` Ron Croonenberg
2013-05-21 19:24           ` Cory Spitz
2013-05-21 19:36             ` Ron Croonenberg [this message]
2013-05-14  0:55 ` [Lustre-devel] Interested in contributing to Lustre Dilger, Andreas
2013-05-14 14:07 ` Cory Spitz

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=519BCCC8.70506@lanl.gov \
    --to=ronc@lanl.gov \
    --cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.