From: "Matt W. Benjamin" <matt@cohortfs.com>
To: "Piotr Dałek" <Piotr.Dalek@ts.fujitsu.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Transaction struct Op
Date: Fri, 3 Jul 2015 10:52:19 -0400 (EDT) [thread overview]
Message-ID: <1440963926.6.1435935139406.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <90559C83A9C7FA45B5846C975DFA612DDB4DD4E243@ABGEX73E.FSC.NET>
I tend to support (++)
----- "Piotr Dałek" <Piotr.Dalek@ts.fujitsu.com> wrote:
> > -----Original Message-----
> > From: Haomai Wang [mailto:haomaiwang@gmail.com]
> > Sent: Thursday, July 02, 2015 7:26 PM
> >
> > Yes, some fields only used for special ops. But union may increase
> the
> > complexity of stuct.
>
> Not by that much, actual changes would be only in coding and encoding,
> rest of the code should remain the same.
>
> > And the extra memory may not a problem because "Ops" in one
> transaction
> > should be within ten.
>
> This equals to at least around 720 bytes that must be stored in RAM
> and transferred through the wire.
>
> With best regards / Pozdrawiam
> Piotr Dałek
> N�����r��y���b�X��ǧv�^�){.n�+���z�]z���{ay�ʇڙ�,j��f���h���z��w������j:+v���w�j�m��������zZ+��ݢj"��
--
Matt Benjamin
CohortFS, LLC.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://cohortfs.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
prev parent reply other threads:[~2015-07-03 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 14:05 Transaction struct Op Dałek, Piotr
2015-07-02 17:26 ` Haomai Wang
2015-07-03 6:31 ` Dałek, Piotr
2015-07-03 14:52 ` Matt W. Benjamin [this message]
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=1440963926.6.1435935139406.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@cohortfs.com \
--cc=Piotr.Dalek@ts.fujitsu.com \
--cc=ceph-devel@vger.kernel.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.