Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: komal <komal@linsyssoft.com>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Compression in DRBD
Date: Wed, 07 Mar 2007 15:46:39 +0530	[thread overview]
Message-ID: <1173262599.2536.25.camel@xenon> (raw)

Hi all,
          Bandwidth is an important issue in DRBD during replication of
data. If bandwidth is properly utilized then replication will be faster
and speed is what everyone needs.
        When bandwidth utilization comes into picture, compressing data
is what
is needed. Earlier discussions were going on to use vtun with a tcp
tunnel with zlib compression factor 9 or so to achieve compression.
        What about implementing compression in DRBD itself. Like using
zlib to
compress each packet and decompress it on receiver side in DRBD code
itself rather than using vtun and all. Wont it solve the purpose? 

Thanks and Regards,
Komal Nawandar.


             reply	other threads:[~2007-03-07 10:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 10:16 komal [this message]
2007-03-07 11:55 ` [Drbd-dev] Compression in DRBD Philipp Reisner
2007-03-07 12:48   ` komal

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=1173262599.2536.25.camel@xenon \
    --to=komal@linsyssoft.com \
    --cc=drbd-dev@lists.linbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox