Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: komal <komal@linsyssoft.com>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Compression in DRBD
Date: Wed, 07 Mar 2007 18:18:08 +0530	[thread overview]
Message-ID: <1173271688.2536.37.camel@xenon> (raw)
In-Reply-To: <200703071255.40086.philipp.reisner@linbit.com>

On Wed, 2007-03-07 at 12:55 +0100, Philipp Reisner wrote:
> Am Mittwoch, 7. März 2007 11:16 schrieb komal:
> > 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?
> >
> 
> Hi,
> 
> DRBD is a really complex piece of software, and I really do not want to
> duplicate anything that can get achieved on other levels.
> 
> Compression on the network can for sure be achieved by other means 
> (outside of DRBD).
> 
> -phil

Hi,

	But if we implement compression in DRBD itself we can have selective
compression. 
	By selective compression I mean is that we will compress only data
packets and not configuration packets (which reports status and
configuration) which cannot be achieved with other compression
techniques. 
	
Thanks and Regards,
Komal


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 10:16 [Drbd-dev] Compression in DRBD komal
2007-03-07 11:55 ` Philipp Reisner
2007-03-07 12:48   ` komal [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=1173271688.2536.37.camel@xenon \
    --to=komal@linsyssoft.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=philipp.reisner@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