[Pvfs2-developers] Pre bmi_mx patch

[Scott Atchley]

Hi Murali,

I have attached a patch that provides for the MX board. It works with  
interactive mode as well as specifying --protocol and --port (and it  
adds --board). It does not work with --iospec and --metaspec.

The option text now looks like:

<snip>
   pvfs2-genconfig can also be executed non-interactively by providing,
   at a minimum, all of the following arguments:

      --logfile     <STRING>     logfile location
      --storage     <STRING>     storage space location
      --quiet                    run silently

   One of the two [] grouped options below must be chosen (for non- 
interactive):

      [
        --protocol    <PROTO>[,<PROTO>..] protocol(s) to use  
(tcp,gm,mx,ib)
        --port        <NUM>      port to use (any single protocol)
        [
          --board     <NUM>      board index number for MX
        ]
        --ioservers   <STRING>   hostnames of data servers.  Can be
                                 <prefix>{#-#,#,#-#,...}
        --metaservers <STRING>   hostnames of meta servers.
      ]
   or
      [
        --iospec      <STRING>   endpoints of data servers. See -- 
spec-usage
        --metaspec    <STRING>   endpoints of meta servers. See -- 
spec-usage
      ]

   The following arguments are entirely optional, whether your  
intention is
   to run pvfs2-genconfig in interactive or non-interactive mode:

      --tcpport     <NUM>               TCP port to use
      --gmport      <NUM>               GM port to use
      --mxboard     <NUM>               MX board to use (default is 0)
      --mxendpoint  <NUM>               MX endpoint to use (default  
is 3)
      --ibport      <NUM>               IB port to use
<snip>

Scott

-------------- next part --------------
A non-text attachment was scrubbed...
Name: genconfig_support_mx_board.patch
Type: application/octet-stream
Size: 5600 bytes
Desc: not available
Url : http://www.beowulf-underground.org/pipermail/pvfs2-developers/attachments/20061228/7bef4803/genconfig_support_mx_board.obj
-------------- next part --------------

On Dec 28, 2006, at 1:45 PM, Scott Atchley wrote:

> Hi Murali,
>
> MX requires -lpthread by default. MX can be configured with -- 
> disable-thread-safety. In that case, it does not require pthreads  
> but performance will be degraded. The bmi_mx code does not use any  
> threads itself, but MX has an internal progression thread that  
> allows overlap between computation and communication.
>
> I can look at modifying pvfs2-genconfig to add the missing board info.
>
> Scott
>
> On Dec 28, 2006, at 1:18 PM, Murali Vilayannur wrote:
>
>> Hi Scott,
>> I see that -lpthread is tacked onto  LIBS regardless of whether we
>> want threading or not. IIRC atleast on the client-side we would want
>> to be able to build without threads although i am not sure if that is
>> true anymore...
>> looks great otherwise.
>> We do need to add the bmi_mx directory so that configure can generate
>> the module.mk file..
>> It would be good to have pvfs2-genconfig generate a default config
>> file which is correct so that people can subsequently edit it if they
>> wish to customize it or something.. does not matter at this point!
>> thanks,
>> Murali
>>
>> On 12/28/06, Scott Atchley <atchley at myri.com> wrote:
>>> Hi all,
>>>
>>> I have attached a patch that modifies the existing PVFS2 CVS  
>>> files so
>>> that they are bmi_mx aware. The modified files are:
>>>
>>> configure.in
>>> include/pvfs2-debug.h
>>> Makefile.in
>>> src/apps/admin/pvfs2-genconfig
>>> src/common/misc/server-config.c
>>> src/io/bmi/bmi.c
>>>
>>> Please review and apply.
>>>
>>> I do not know if you need to create a src/io/bmi/bmi_mx directory so
>>> that configure can make src/io/bmi/bmi_mx/module.mk.
>>>
>>> For bmi_mx, we need to specify a peername (aka uri spec) that
>>> includes hostname, board (NIC) index, and MX endpoint (analogous to
>>> port). The current uri specs (tcp, gm, ib) only include hostname and
>>> port. I modified src/apps/admin/pvfs2-genconfig only enough to get
>>> the MX endpoint but I did not have it get the board id.  
>>> Therefore, it
>>> generates incorrect peernames (mx://myhost:3 instead of mx://myhost:
>>> 0:3 as needed). Let me know if you want me to modify it or if you
>>> would rather someone else do it. Currently, I am simply editing
>>> fs.conf and server.conf after running pvfs2-genconfig.
>>>
>>> Thanks,
>>>
>>> Scott
>>>
>>>
>>>
>>> _______________________________________________
>>> Pvfs2-developers mailing list
>>> Pvfs2-developers at beowulf-underground.org
>>> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
>>>
>>>
>>>
>>>
>
> _______________________________________________
> Pvfs2-developers mailing list
> Pvfs2-developers at beowulf-underground.org
> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers