All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] Re: [DRBD-cvs] r1600 - branches/drbd-0.7/drbd
Date: Tue, 19 Oct 2004 11:30:24 +0200	[thread overview]
Message-ID: <200410191130.24197.philipp.reisner@linbit.com> (raw)
In-Reply-To: <20041019091152.50E053BE6D@garcon.linbit.com>

On Tuesday 19 October 2004 11:11, svn@svn.drbd.org wrote:
> Author: lars
> Date: 2004-10-19 11:11:49 +0200 (Tue, 19 Oct 2004)
> New Revision: 1600
>
> Modified:
>    branches/drbd-0.7/drbd/drbd_int.h
>    branches/drbd-0.7/drbd/drbd_main.c
>    branches/drbd-0.7/drbd/drbd_receiver.c
>    branches/drbd-0.7/drbd/drbd_req.c
>    branches/drbd-0.7/drbd/drbd_worker.c
> Log:
> get rid of the HERE macro
> provide (experimental) code for decreasing latency on 2.6 kernels by
> pushing the tcp stack
>

Hi Lars,

Do you really think it is an good idea to put that tcp-stack pushing
into drbd-0.7 ??

- Do you know that it improves performance ? 
  Or is it just an assumption.

- Do we really want to do this with the stable code 
  I think we should have a least one or two reports from the list,
  that 
    a) it does not break anything
    b) it improves performance.

-philipp
-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria    http://www.linbit.com :

       reply	other threads:[~2004-10-19  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041019091152.50E053BE6D@garcon.linbit.com>
2004-10-19  9:30 ` Philipp Reisner [this message]
2004-10-19 10:03   ` [Drbd-dev] Re: [DRBD-cvs] r1600 - branches/drbd-0.7/drbd Lars Ellenberg
2004-10-19 10:40     ` Philipp Reisner

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=200410191130.24197.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.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 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.