Re: Ipv6 - performance results on red hat linux.

From: Steve Phillips (steve_at_focb.co.nz)
Date: 11/18/03

  • Next message: cajun: "OT: Anyone else had trouble receiving from the list??"
    To: redhat-list@redhat.com
    Date: Wed, 19 Nov 2003 09:19:33 +1300 (NZDT)
    
    

    Your question seems a little vague but you may want to look at this link..

    http://homepages.fh-regensburg.de/~jom30197/

    What you are asking for here does not really appear to make a lot of sense
    - things such as IPv4 vs IPv6 are ok to compare, as these tend to be
    similar things (IP Stacks) but IPsec happens at a different layer unless
    you are talking about comparing IPv4 with no IPsec vs IPv4 with IPsec with
    the tunnels terminating on the device you are testing and the
    encapsulation happening there.

    The processes then would tend to be CPU bound, not protocol stack bound so
    repeating the same tests with IPv6 should produce the same differences
    which show the overhead with adding IPsec encryption to the system.

    You also need to ensure that you are not testing dissimilar systems, and
    if the link above has truth to it, you may get slightly improved
    throughput/performance using an IPv6 stack over an IPv4 one, but it is
    again very subjective and the difference in values are probably negigable
    in 99.9% of all environments.

    (also note - RedHat Linux or another brand of linux will produce extremely
    similar statistics - the one used above was SuSe but one linux is
    essentually the same for these purposes.)

    -- 
    Steve.
    >
    > Hello everybody,
    >
    > Good day to every body.
    >
    > Could any body share the Linux stack Ipv6 raw performance results/numbers
    > in
    > red hat linux platform.
    >
    > the performance parameters are -
    >
    > Ipv6 forwarding (with ipsecurity/without)-
    > Latency(with ipsec/with)-
    > Throughput(with ipsec/without)-
    >
    > -Thanks and warm regds,
    > Srinivas .k
    >
    >
    >
    >
    >
    >
    > ***************************************************************************
    > This message is proprietary to Future Software Limited (FSL)
    > and is intended solely for the use of the individual to whom it
    > is addressed. It may contain  privileged or confidential information
    > and should not be circulated or used for any purpose other than for
    > what it is intended.
    >
    > If you have received this message in error, please notify the
    > originator immediately. If you are not the intended recipient,
    > you are notified that you are strictly prohibited from using,
    > copying, altering, or disclosing the contents of this message.
    > FSL accepts no responsibility for loss or damage arising from
    > the use of the information transmitted by this email including
    > damage from virus.
    > ***************************************************************************
    >
    >
    > --
    > redhat-list mailing list
    > unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    > https://www.redhat.com/mailman/listinfo/redhat-list
    >
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: cajun: "OT: Anyone else had trouble receiving from the list??"

    Relevant Pages

    • Re: ipsec
      ... Is there an working implementation of ipsec over IPv6? ... so instead of sending data via Berkley sockets etc, or maybe the stack ... for AH and ESP depending on whether IPSec is used in IPv4 and IPv6, ...
      (comp.security.firewalls)
    • ipsec
      ... Is there an working implementation of ipsec over IPv6? ... For example so instead of sending data via Berkley sockets etc, or maybe the stack handles it for me? ...
      (comp.security.firewalls)
    • Re: [fw-wiz] IPv6 and IPSec
      ... > require IPSec? ... And "support" can be a nebulus thing. ... all of IPv4 in toto. ... And something like 40 million IPv6 networks are routable in the ...
      (Firewall-Wizards)
    • Re: pthread questions
      ... > linux") people might be able to help you a little better. ... the shared libraries and search their symbols. ... since the simple stabs debug info format is completely GONE ... DWARF2 defines a stack machine, ...
      (comp.os.linux.development.system)
    • Stack Size for a Thread
      ... How can i know the default Stack Size allocated to a Thread in Red Hat ... The same application worked fine when the Heap size was reduced to ... However the application worked fine in another linux box with the same ...
      (comp.os.linux.misc)