All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alphe Salas Michels <asalas@kepler.cl>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Sage Weil <sage@inktank.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: writing a ceph cliente for MS windows
Date: Tue, 05 Nov 2013 19:31:41 -0300	[thread overview]
Message-ID: <527971CD.1010705@kepler.cl> (raw)
In-Reply-To: <CABBk=J8gfR0CDQ4fuHmXtkH5Fe3kKOGTi7YgixB7ZSL1JHkYXg@mail.gmail.com>

Hello sage and Yehuda,
yes nwat told me that u64 was an alias for unsigned long which is 
default C compiler data type.
I wasn't cautious.

I read some other things like the cygwin mount.cc /mount.h files ... 
they include cifs and nfs filetype things like samba too. We could 
integrate a new data type in it with our ceph-win32-client.

Obviously everyone would prefere something with a nice point and click 
window to setup their ceph-win32-client. But as a starter... maybe we 
could understand better the way windows handle file systems starting 
from cygwin/mount files.

Regards,
signature

*Alphé Salas*
Ingeniero T.I

asalas@kepler.cl*<http://www.kepler.cl>*

On 11/05/13 18:59, Yehuda Sadeh wrote:
> On Tue, Nov 5, 2013 at 1:49 PM, Alphe Salas Michels<asalas@kepler.cl>  wrote:
>> Hello sage,
>> I followed your lead and went a bit further in my source code reading and I
>> notice serveral problems:
>> first most of the id use in ceph osd_clients, mds_clients, mon_client use
>> the data type u64 which will be a problem
>> as most of the windows in use are windows XP or Windows server 2003 in 32
>> bits. As they are used for id tag for
>> things like snapshot pages (if I understand well) that can be a problem for
>> a port no?
>>
>> What I read so far was
>> mount.ceph files > kernel/fs/ceph files which contains the mds_client files
>> and the kernel ioctl interface ... >  include / linux / ceph  files which
>> integrates libcephfs.h. and all the needed files
>>
>> there is three clients, there is auth.h a messenger, a msgpool, buffer,
>> rados that depends on msgr that include in every aspect of the messages
>> formation  one or more __le64 message.
>>
>> I m far from understanding the whole code and the interactions betwin all
>> the files and which we can skip and which we can keep.
>>
>> how can we translate those data type into 32bit in order for ceph cluster to
>> understand them and ceph-windows-client to transmit them?
> It is possible to define 64 bit variables on 32 bit architectures. The
> compiler handles it for you.
>
> Yehuda
>
>

--
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

  reply	other threads:[~2013-11-05 22:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 20:19 writing a ceph cliente for MS windows Alphe Salas Michels
2013-11-05 14:23 ` Sage Weil
2013-11-05 17:40   ` Alphe Salas Michels
2013-11-05 21:49     ` Alphe Salas Michels
2013-11-05 21:59       ` Yehuda Sadeh
2013-11-05 22:31         ` Alphe Salas Michels [this message]
2013-11-06  0:00     ` Sage Weil
2013-11-06 14:37       ` Alphe Salas Michels
2013-11-06 21:47       ` Alphe Salas Michels
2013-11-05 23:33 ` James Harper
     [not found] <CAME-gASugOE=-ZoY3-sAa4vCzOd+TXBiEavjoUH3gDLG+1K38w@mail.gmail.com>
2013-11-07 12:13 ` Alphe Salas Michels
2013-11-07 14:29   ` Ketor D
2013-11-07 14:50     ` Matt W. Benjamin
2013-11-07 18:02       ` Alphe Salas Michels
2013-11-07 20:47         ` Alphe Salas Michels
2013-11-08  0:11           ` Malcolm Haak
2013-11-08  0:31             ` Matt W. Benjamin
     [not found]             ` <CAME-gARbjR++qXsx9Sx4KbuggthONrscHToxCTUKrci_MLMDzw@mail.gmail.com>
2013-11-08 14:15               ` Alphe Salas Michels
2014-12-26 17:10                 ` Ketor D
2014-12-27  5:14                   ` Dong Yuan
2014-12-27  5:14                     ` Dong Yuan

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=527971CD.1010705@kepler.cl \
    --to=asalas@kepler.cl \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@inktank.com \
    --cc=yehuda@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.