emperor leftovers

emperor leftovers

[Sage Weil]

There are several blueprints that were put together for emperor even 
though we didn't have the developer time to actually do them.  For anyone 
interested in getting involved in Ceph development, these may present an 
easy way to get involved in the process.  If you're interested in 
adopting any of these orphan blueprints, speak up and we can make sure it 
gets onto the firefly CDS schedule.

In (very) approximate order of difficulty:

http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Source_tree_restructuring
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_shared_read_cache
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_namespace_support
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_copy-on-read_for_clones
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_dumpability
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/osd%3A_clone_from_journal_on_btrfs
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_reduce_memory_consumption

sage

Re: emperor leftovers

[Patrick McGarry]

I have moved all of these to our new development "sideboard" [1] which
can be used to store blueprints that don't make major releases.
Alternately, if you have an idea and want help fleshing it out, this
would be a great place to drop a blueprint for community
collaboration.

[1] http://wiki.ceph.com/01Planning/Sideboard



Best Regards,

Patrick McGarry
Director, Community || Inktank
http://ceph.com  ||  http://inktank.com
@scuttlemonkey || @ceph || @inktank


On Thu, Nov 7, 2013 at 10:05 AM, Sage Weil <sage@inktank.com> wrote:
> There are several blueprints that were put together for emperor even
> though we didn't have the developer time to actually do them.  For anyone
> interested in getting involved in Ceph development, these may present an
> easy way to get involved in the process.  If you're interested in
> adopting any of these orphan blueprints, speak up and we can make sure it
> gets onto the firefly CDS schedule.
>
> In (very) approximate order of difficulty:
>
> http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Source_tree_restructuring
> http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_shared_read_cache
> http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_namespace_support
> http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_copy-on-read_for_clones
> http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_dumpability
> http://wiki.ceph.com/01Planning/02Blueprints/Emperor/osd%3A_clone_from_journal_on_btrfs
> http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_reduce_memory_consumption
>
> sage
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: emperor leftovers

[Sage Weil]

The portability blueprint isn't complete, but is also well underway.  That 
may merit a quick session to discuss the balance of the summit.  I'm also 
curious if the discussion on windows portability is relevant here or if 
it's better treated as a separate but related effort.  I suspect making 
things like cephfs and librados build on windows will mean providing 
alternate implemantations of things like Mutex, Cond, Thread, and so 
forth.

Others:

http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rgw%3A_multitenancy
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rgw%3A_bucket_index_scalability
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rgw%3A_plugin_architecture
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Create_and_Maintain_S3_feature_list_for_compatibility_tracking
http://wiki.ceph.com/01Planning/02Blueprints/Dumpling/Client_Security_for_CephFS
http://wiki.ceph.com/01Planning/02Blueprints/Dumpling/create_crush_library

sage

On Thu, 7 Nov 2013, Patrick McGarry wrote:

> I have moved all of these to our new development "sideboard" [1] which
> can be used to store blueprints that don't make major releases.
> Alternately, if you have an idea and want help fleshing it out, this
> would be a great place to drop a blueprint for community
> collaboration.
> 
> [1] http://wiki.ceph.com/01Planning/Sideboard
> 
> 
> 
> Best Regards,
> 
> Patrick McGarry
> Director, Community || Inktank
> http://ceph.com  ||  http://inktank.com
> @scuttlemonkey || @ceph || @inktank
> 
> 
> On Thu, Nov 7, 2013 at 10:05 AM, Sage Weil <sage@inktank.com> wrote:
> > There are several blueprints that were put together for emperor even
> > though we didn't have the developer time to actually do them.  For anyone
> > interested in getting involved in Ceph development, these may present an
> > easy way to get involved in the process.  If you're interested in
> > adopting any of these orphan blueprints, speak up and we can make sure it
> > gets onto the firefly CDS schedule.
> >
> > In (very) approximate order of difficulty:
> >
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Source_tree_restructuring
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_shared_read_cache
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_namespace_support
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/rbd%3A_copy-on-read_for_clones
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_dumpability
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/osd%3A_clone_from_journal_on_btrfs
> > http://wiki.ceph.com/01Planning/02Blueprints/Emperor/mds%3A_reduce_memory_consumption
> >
> > sage
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Re: emperor leftovers

[Noah Watkins]

On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com> wrote:

> curious if the discussion on windows portability is relevant here or if
> it's better treated as a separate but related effort.

The kernel space talk that's been tossed around probably isn't
relevant, but I'd be nice to learn about cygwin porting if anyone has
knowledge in this area.

Re: emperor leftovers

[Matt W. Benjamin]

Yes.  But you may wish to think about mingwXX porting rather than Cygwin,
if you prefer native results.

Matt

----- "Noah Watkins" <noah.watkins@inktank.com> wrote:

> On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com> wrote:
> 
> > curious if the discussion on windows portability is relevant here or
> if
> > it's better treated as a separate but related effort.
> 
> The kernel space talk that's been tossed around probably isn't
> relevant, but I'd be nice to learn about cygwin porting if anyone has
> knowledge in this area.
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

Re: emperor leftovers

[Matt W. Benjamin]

Or, MSVC, frankly.

----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:

> Yes.  But you may wish to think about mingwXX porting rather than
> Cygwin,
> if you prefer native results.
> 
> Matt
> 
> ----- "Noah Watkins" <noah.watkins@inktank.com> wrote:
> 
> > On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com> wrote:
> > 
> > > curious if the discussion on windows portability is relevant here
> or
> > if
> > > it's better treated as a separate but related effort.
> > 
> > The kernel space talk that's been tossed around probably isn't
> > relevant, but I'd be nice to learn about cygwin porting if anyone
> has
> > knowledge in this area.
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> ceph-devel"
> > in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -- 
> Matt Benjamin
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
> 
> http://linuxbox.com
> 
> tel.  734-761-4689 
> fax.  734-769-8938 
> cel.  734-216-5309 
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

Re: emperor leftovers

[Noah Watkins]

Oh, my ignorance of Windows development is enormous :) So there are cygwin, mingw, and msvc. And mingw “more” native than cygwin, but doesn’t try to do posix, and msvc just the default/native windows development env?

On Nov 7, 2013, at 5:34 PM, Matt W. Benjamin <matt@linuxbox.com> wrote:

> Or, MSVC, frankly.
> 
> ----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:
> 
>> Yes.  But you may wish to think about mingwXX porting rather than
>> Cygwin,
>> if you prefer native results.
>> 
>> Matt
>> 
>> ----- "Noah Watkins" <noah.watkins@inktank.com> wrote:
>> 
>>> On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com> wrote:
>>> 
>>>> curious if the discussion on windows portability is relevant here
>> or
>>> if
>>>> it's better treated as a separate but related effort.
>>> 
>>> The kernel space talk that's been tossed around probably isn't
>>> relevant, but I'd be nice to learn about cygwin porting if anyone
>> has
>>> knowledge in this area.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>> ceph-devel"
>>> in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> 
>> -- 
>> Matt Benjamin
>> The Linux Box
>> 206 South Fifth Ave. Suite 150
>> Ann Arbor, MI  48104
>> 
>> http://linuxbox.com
>> 
>> tel.  734-761-4689 
>> fax.  734-769-8938 
>> cel.  734-216-5309 
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -- 
> Matt Benjamin
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
> 
> http://linuxbox.com
> 
> tel.  734-761-4689 
> fax.  734-769-8938 
> cel.  734-216-5309 

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: emperor leftovers

[Matt W. Benjamin]

Hi,

Mingw can do posix -threads-, nowadays it has something internal, but
probably better is a standalone winpthread.h one-file shim (depending on
what level of conformance you care about, perhaps not much).
But yes, doesn't provide a posix env (which generally is not a going
to lead to a first class port).

MSVC is the default windows env.  It's probably the ideal, despite most
requirement for moving furthest towards the windows mindset.  It has better
open source tool support than you might expect.

Matt

----- "Noah Watkins" <noahwatkins@gmail.com> wrote:

> Oh, my ignorance of Windows development is enormous :) So there are
> cygwin, mingw, and msvc. And mingw “more” native than cygwin, but
> doesn’t try to do posix, and msvc just the default/native windows
> development env?
> 
> On Nov 7, 2013, at 5:34 PM, Matt W. Benjamin <matt@linuxbox.com>
> wrote:
> 
> > Or, MSVC, frankly.
> > 
> > ----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:
> > 
> >> Yes.  But you may wish to think about mingwXX porting rather than
> >> Cygwin,
> >> if you prefer native results.
> >> 
> >> Matt
> >> 
> >> ----- "Noah Watkins" <noah.watkins@inktank.com> wrote:
> >> 
> >>> On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com>
> wrote:
> >>> 
> >>>> curious if the discussion on windows portability is relevant
> here
> >> or
> >>> if
> >>>> it's better treated as a separate but related effort.
> >>> 
> >>> The kernel space talk that's been tossed around probably isn't
> >>> relevant, but I'd be nice to learn about cygwin porting if anyone
> >> has
> >>> knowledge in this area.
> >>> --
> >>> To unsubscribe from this list: send the line "unsubscribe
> >> ceph-devel"
> >>> in
> >>> the body of a message to majordomo@vger.kernel.org
> >>> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> >> 
> >> -- 
> >> Matt Benjamin
> >> The Linux Box
> >> 206 South Fifth Ave. Suite 150
> >> Ann Arbor, MI  48104
> >> 
> >> http://linuxbox.com
> >> 
> >> tel.  734-761-4689 
> >> fax.  734-769-8938 
> >> cel.  734-216-5309 
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe
> ceph-devel"
> >> in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> > -- 
> > Matt Benjamin
> > The Linux Box
> > 206 South Fifth Ave. Suite 150
> > Ann Arbor, MI  48104
> > 
> > http://linuxbox.com
> > 
> > tel.  734-761-4689 
> > fax.  734-769-8938 
> > cel.  734-216-5309

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: emperor leftovers

[Noah Watkins]

On Nov 7, 2013, at 5:47 PM, Matt W. Benjamin <matt@linuxbox.com> wrote:

> MSVC is the default windows env.  It's probably the ideal, despite most
> requirement for moving furthest towards the windows mindset.  It has better
> open source tool support than you might expect.

Cool, thanks for the clarification. This might be a good reason for the source code reorganization blueprint, assuming part of its goals are to be able to build Ceph in components. Being able to work on just porting, say, librados, would be nice/easier.

http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Source_tree_restructuring

> 
> Matt
> 
> ----- "Noah Watkins" <noahwatkins@gmail.com> wrote:
> 
>> Oh, my ignorance of Windows development is enormous :) So there are
>> cygwin, mingw, and msvc. And mingw “more” native than cygwin, but
>> doesn’t try to do posix, and msvc just the default/native windows
>> development env?
>> 
>> On Nov 7, 2013, at 5:34 PM, Matt W. Benjamin <matt@linuxbox.com>
>> wrote:
>> 
>>> Or, MSVC, frankly.
>>> 
>>> ----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:
>>> 
>>>> Yes.  But you may wish to think about mingwXX porting rather than
>>>> Cygwin,
>>>> if you prefer native results.
>>>> 
>>>> Matt
>>>> 
>>>> ----- "Noah Watkins" <noah.watkins@inktank.com> wrote:
>>>> 
>>>>> On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com>
>> wrote:
>>>>> 
>>>>>> curious if the discussion on windows portability is relevant
>> here
>>>> or
>>>>> if
>>>>>> it's better treated as a separate but related effort.
>>>>> 
>>>>> The kernel space talk that's been tossed around probably isn't
>>>>> relevant, but I'd be nice to learn about cygwin porting if anyone
>>>> has
>>>>> knowledge in this area.
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>> ceph-devel"
>>>>> in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at 
>> http://vger.kernel.org/majordomo-info.html
>>>> 
>>>> -- 
>>>> Matt Benjamin
>>>> The Linux Box
>>>> 206 South Fifth Ave. Suite 150
>>>> Ann Arbor, MI  48104
>>>> 
>>>> http://linuxbox.com
>>>> 
>>>> tel.  734-761-4689 
>>>> fax.  734-769-8938 
>>>> cel.  734-216-5309 
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe
>> ceph-devel"
>>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> 
>>> -- 
>>> Matt Benjamin
>>> The Linux Box
>>> 206 South Fifth Ave. Suite 150
>>> Ann Arbor, MI  48104
>>> 
>>> http://linuxbox.com
>>> 
>>> tel.  734-761-4689 
>>> fax.  734-769-8938 
>>> cel.  734-216-5309
> 
> -- 
> Matt Benjamin
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
> 
> http://linuxbox.com
> 
> tel.  734-761-4689 
> fax.  734-769-8938 
> cel.  734-216-5309

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: emperor leftovers

[Cesar Mello]

Yes MSVC and straight win32 is the rock solid way to go. That's where I
would put my late night effort to help.

Best regards
Mello

Enviado pelo meu Windows Phone De: Matt W. Benjamin
Enviada em: 07/11/2013 23:34
Para: Noah Watkins
Cc: Patrick McGarry; Ceph Devel; Noah Watkins; Sage Weil; Cesar Mello
Assunto: Re: emperor leftovers
Or, MSVC, frankly.

----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:

> Yes.  But you may wish to think about mingwXX porting rather than
> Cygwin,
> if you prefer native results.
>
> Matt
>
> ----- "Noah Watkins" <noah.watkins@inktank.com> wrote:
>
> > On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com> wrote:
> >
> > > curious if the discussion on windows portability is relevant here
> or
> > if
> > > it's better treated as a separate but related effort.
> >
> > The kernel space talk that's been tossed around probably isn't
> > relevant, but I'd be nice to learn about cygwin porting if anyone
> has
> > knowledge in this area.
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> ceph-devel"
> > in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
> --
> Matt Benjamin
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
>
> http://linuxbox.com
>
> tel.  734-761-4689
> fax.  734-769-8938
> cel.  734-216-5309
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689
fax.  734-769-8938
cel.  734-216-5309

RE: emperor leftovers

[Sage Weil]

On Thu, 7 Nov 2013, Cesar Mello wrote:
> Yes MSVC and straight win32 is the rock solid way to go. That's where I
> would put my late night effort to help.

Me too.  I think the main primitives (mutex, cond, thread) are already 
well abstracted, so hopefully this is a matter of providing win32 (is it 
really still called that??) implementations and adding new wrappers for 
other components as needed.

sage

> 
> Best regards
> Mello
> 
> Enviado pelo meu Windows Phone De: Matt W. Benjamin
> Enviada em: 07/11/2013 23:34
> Para: Noah Watkins
> Cc: Patrick McGarry; Ceph Devel; Noah Watkins; Sage Weil; Cesar Mello
> Assunto: Re: emperor leftovers
> Or, MSVC, frankly.
> 
> ----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:
> 
> > Yes.  But you may wish to think about mingwXX porting rather than
> > Cygwin,
> > if you prefer native results.
> >
> > Matt
> >
> > ----- "Noah Watkins" <noah.watkins@inktank.com> wrote:
> >
> > > On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com> wrote:
> > >
> > > > curious if the discussion on windows portability is relevant here
> > or
> > > if
> > > > it's better treated as a separate but related effort.
> > >
> > > The kernel space talk that's been tossed around probably isn't
> > > relevant, but I'd be nice to learn about cygwin porting if anyone
> > has
> > > knowledge in this area.
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe
> > ceph-devel"
> > > in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> > --
> > Matt Benjamin
> > The Linux Box
> > 206 South Fifth Ave. Suite 150
> > Ann Arbor, MI  48104
> >
> > http://linuxbox.com
> >
> > tel.  734-761-4689
> > fax.  734-769-8938
> > cel.  734-216-5309
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> > in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -- 
> Matt Benjamin
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
> 
> http://linuxbox.com
> 
> tel.  734-761-4689
> fax.  734-769-8938
> cel.  734-216-5309
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Re: emperor leftovers

[Alphe Salas Michels]

I started reading the libcepfs related code. and it is still a hudge task.
Cygwin seems to me to be the more complete set of ported gnu libraries 
to win32.

MSVC is not the tool I will use for the port ... since your work is 
slown and hidden most
of the time below a tons of click to do thingies...

Code:block /mingWin or cygwin seems to me the more producing perspective.
first it is closer to tools used by linux developers.

A full porting to Win32 meas you will have to write ceph code in 
microsoft compilers C++ or .NET
ways, then you will have to write a port in the same way for each side 
libraries that ceph use
and that doesn t exists on MS windows visual studio stuffs...
I m not talking about adapting cout << "you're a coder be happy"; but 
rather adapting pthread lib which is everywhere in ceph code.
that can be done... but if it is already done why not using it ?


But truelly the biggest problem in ceph world is that we have two 
concurent ways to access
the data on ceph. As far as I understand rbd and cephfs are not 
compatible you can t see what
the other did.

We have Rbd and ceph-fs/ceph-fuse so who use what? for what purpose? 
with what results?
 From that depends what a client port to windows will be.
Can we port everything ceph is on windows? well ceph is a hudge project. 
just a quick isolation
of files related to libcephfs.cc shows a 400+ files. Now I try to see if 
all those files are needed and if
that number can be reduced.

Regards

signature

*Alphé Salas*
Ingeniero T.I


On 11/08/13 02:24, Sage Weil wrote:
> On Thu, 7 Nov 2013, Cesar Mello wrote:
>> Yes MSVC and straight win32 is the rock solid way to go. That's where I
>> would put my late night effort to help.
> Me too.  I think the main primitives (mutex, cond, thread) are already
> well abstracted, so hopefully this is a matter of providing win32 (is it
> really still called that??) implementations and adding new wrappers for
> other components as needed.
>
> sage
>
>> Best regards
>> Mello
>>
>> Enviado pelo meu Windows Phone De: Matt W. Benjamin
>> Enviada em: 07/11/2013 23:34
>> Para: Noah Watkins
>> Cc: Patrick McGarry; Ceph Devel; Noah Watkins; Sage Weil; Cesar Mello
>> Assunto: Re: emperor leftovers
>> Or, MSVC, frankly.
>>
>> ----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:
>>
>>> Yes.  But you may wish to think about mingwXX porting rather than
>>> Cygwin,
>>> if you prefer native results.
>>>
>>> Matt
>>>
>>> ----- "Noah Watkins" <noah.watkins@inktank.com> wrote:
>>>
>>>> On Thu, Nov 7, 2013 at 5:15 PM, Sage Weil <sage@inktank.com> wrote:
>>>>
>>>>> curious if the discussion on windows portability is relevant here
>>> or
>>>> if
>>>>> it's better treated as a separate but related effort.
>>>> The kernel space talk that's been tossed around probably isn't
>>>> relevant, but I'd be nice to learn about cygwin porting if anyone
>>> has
>>>> knowledge in this area.
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe
>>> ceph-devel"
>>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> --
>>> Matt Benjamin
>>> The Linux Box
>>> 206 South Fifth Ave. Suite 150
>>> Ann Arbor, MI  48104
>>>
>>> http://linuxbox.com
>>>
>>> tel.  734-761-4689
>>> fax.  734-769-8938
>>> cel.  734-216-5309
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
>>> in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> -- 
>> Matt Benjamin
>> The Linux Box
>> 206 South Fifth Ave. Suite 150
>> Ann Arbor, MI  48104
>>
>> http://linuxbox.com
>>
>> tel.  734-761-4689
>> fax.  734-769-8938
>> cel.  734-216-5309
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" 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 ceph-devel" 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 ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html