From: Alphe Salas Michels <asalas@kepler.cl>
To: Sage Weil <sage@inktank.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: emperor leftovers
Date: Tue, 26 Nov 2013 18:46:50 -0300 [thread overview]
Message-ID: <529516CA.3000505@kepler.cl> (raw)
In-Reply-To: <alpine.DEB.2.00.1311072123240.17150@cobra.newdream.net>
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
next prev parent reply other threads:[~2013-11-26 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 2:38 emperor leftovers Cesar Mello
2013-11-08 5:24 ` Sage Weil
2013-11-26 21:46 ` Alphe Salas Michels [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-07 15:05 Sage Weil
2013-11-07 15:30 ` Patrick McGarry
2013-11-08 1:15 ` Sage Weil
2013-11-08 1:29 ` Noah Watkins
2013-11-08 1:33 ` Matt W. Benjamin
2013-11-08 1:34 ` Matt W. Benjamin
2013-11-08 1:40 ` Noah Watkins
2013-11-08 1:47 ` Matt W. Benjamin
2013-11-08 1:53 ` Noah Watkins
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=529516CA.3000505@kepler.cl \
--to=asalas@kepler.cl \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
/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.