05 Oct, 2009

1 commit

  • It is not currently possible to instruct pktgen to use one selected tx queue.

    When Robert added multiqueue support in commit 45b270f8, he added
    an interval (queue_map_min, queue_map_max), and his code doesnt take
    into account the case of min = max, to select one tx queue exactly.

    I suspect a high performance setup on a eight txqueue device wants
    to use exactly eight cpus, and assign one tx queue to each sender.

    This patchs makes pktgen select the right tx queue, not the first one.

    Also updates Documentation to reflect Robert changes.

    Signed-off-by: Eric Dumazet
    Signed-off-by: Robert Olsson
    Signed-off-by: David S. Miller

    Eric Dumazet
     

03 Oct, 2009

1 commit


21 Sep, 2009

1 commit


05 Sep, 2009

1 commit

  • This patch introduces a new sysctl option to make IPv4 Address Scoping
    configurable .

    In networking environments where DNAT rules in iptables prerouting
    chains convert destination IP's to link-local/private IP addresses,
    SCTP connections fail to establish as the INIT chunk is dropped by the
    kernel due to address scope match failure.
    For example to support overlapping IP addresses (same IP address with
    different vlan id) a Layer-5 application listens on link local IP's,
    and there is a DNAT rule that maps the destination IP to a link local
    IP. Such applications never get the SCTP INIT if the address-scoping
    draft is strictly followed.

    This sysctl configuration allows SCTP to function in such
    unconventional networking environments.

    Sysctl options:
    0 - Disable IPv4 address scoping draft altogether
    1 - Enable IPv4 address scoping (default, current behavior)
    2 - Enable address scoping but allow IPv4 private addresses in init/init-ack
    3 - Enable address scoping but allow IPv4 link local address in init/init-ack

    Signed-off-by: Bhaskar Dutta
    Signed-off-by: Vlad Yasevich

    Bhaskar Dutta
     

02 Sep, 2009

1 commit


20 Aug, 2009

1 commit


13 Aug, 2009

1 commit


28 Jul, 2009

1 commit


27 Jul, 2009

1 commit


18 Jul, 2009

1 commit


15 Jun, 2009

1 commit


13 Jun, 2009

1 commit


12 Jun, 2009

1 commit

  • Commit b00055aacdb172c05067612278ba27265fcd05ce " [NET] core: add
    RFC2863 operstate" defined new interface flag values. Its
    documentation specified that these flags could be accessed from user
    space via SIOCGIFFLAGS. However, this does not work because the new
    flags do not fit in that ioctl's argument width.

    Change the documentation to match the code's behavior. Also change
    the source to explicitly show the truncation. This _should_ have no
    effect on executable code, and did not with gcc 4.2.4 generating x86
    code.

    A new ioctl could be defined to return all interface flags to user
    space. However, since this has been broken for three years with no
    one complaining, there doesn't seem much need. They are still
    accessible via netlink.

    Reported-by: "Fredrik Arnerup"
    Signed-off-by: John Dykstra
    Signed-off-by: David S. Miller

    John Dykstra
     

09 Jun, 2009

1 commit


01 Jun, 2009

1 commit

  • Add 'autoconf' and 'disable_ipv6' parameters to the IPv6 module.

    The first controls if IPv6 addresses are autoconfigured from
    prefixes received in Router Advertisements. The IPv6 loopback
    (::1) and link-local addresses are still configured.

    The second controls if IPv6 addresses are desired at all. No
    IPv6 addresses will be added to any interfaces.

    Signed-off-by: Brian Haley
    Signed-off-by: David S. Miller

    Brian Haley
     

19 May, 2009

3 commits


18 May, 2009

1 commit


05 May, 2009

1 commit

  • This should be very safe compared with full enabled, so I see
    no reason why it shouldn't be done right away. As ECN can only
    be negotiated if the SYN sending party is also supporting it,
    somebody in the loop probably knows what he/she is doing. If
    SYN does not ask for ECN, the server side SYN-ACK is identical
    to what it is without ECN. Thus it's quite safe.

    The chosen value is safe w.r.t to existing configs which
    choose to currently set manually either 0 or 1 but
    silently upgrades those who have not explicitly requested
    ECN off.

    Whether to just enable both sides comes up time to time but
    unless that gets done now we can at least make the servers
    aware of ECN already. As there are some known problems to occur
    if ECN is enabled, it's currently questionable whether there's
    any real gain from enabling clients as servers mostly won't
    support it anyway (so we'd hit just the negative sides). After
    enabling the servers and getting that deployed, the client end
    enable really has some potential gain too.

    Signed-off-by: Ilpo Järvinen
    Signed-off-by: David S. Miller

    Ilpo Järvinen
     

23 Apr, 2009

1 commit


13 Apr, 2009

1 commit

  • Fix a zero address hole bug in the bonding arp_ip_target list
    that was causing the bond to ignore ARP replies (bugz 13006).
    Instead of just setting the array entry to zero, we now
    copy any additional entries down one slot, putting the
    zero entry at the end. With this change we can now have
    all the loops that walk the array stop when they hit a zero
    since there will be no addresses after it.

    Changes are based in part on code fragment provided in kernel:
    bugzilla 13006:

    http://bugzilla.kernel.org/show_bug.cgi?id=13006

    by Steve Howard

    Signed-off-by: Brian Haley
    Signed-off-by: Jay Vosburgh
    Signed-off-by: David S. Miller

    Brian Haley
     

02 Apr, 2009

1 commit

  • - vxge driver help text file.

    - No change from previous submission.

    - Changes in previous submissions -
    Removed the performance tuning section with instructions to disable
    time stamps and change sysctl settings - Reported by Dave Miller
    General clean up.
    - Removed tx/rx_pause, exec_mode, tx_steering_type, rx_steering_type, gro,
    intr_type, rx & tx max_indicate_pkts and exec_mode loadable parameters. The
    driver default settings work well in most if not all cases. Another patch
    to configure these parameters with ethtool will be released in the future -
    Reported by Stephen Hemminger.
    - Incorporated following fixes based on comments from Ben Hutchings
    Removed references to earlier kernel versions.
    Removed sections that are similar for all drivers -
    Load/Unload
    Identifying the adapter/interface
    Boot time configuration
    Removed loadable parameter -
    NAPI - Napi is always enabled.
    rx_steering_type & ring_blocks - The driver default settings
    work well in most if not all cases. Another patch to configure
    these parameters with ethtool will be released in the future.
    Removed ethtool support section - No need to duplicate ethtool
    docs here.
    Removed Known Issue on SUSE 9 - Doesn't apply when using a
    current kernel.
    Removed Common Problems section - These don't apply to in-tree modules.
    Removed Available Downloads section - Not sure this belongs in-tree.
    Removed Copyright information - This notice doesn't belong in
    the kernel.

    Signed-off-by: Sivakumar Subramani
    Signed-off-by: Rastapur Santosh
    Signed-off-by: Ramkrishna Vepa
    Signed-off-by: David S. Miller

    Ramkrishna Vepa
     

19 Mar, 2009

1 commit

  • Fix the behavior of allowing both sysctl and addrconf_dad_failure()
    to set the disable_ipv6 parameter without any bad side-effects.
    If DAD fails and accept_dad > 1, we will still set disable_ipv6=1,
    but then instead of allowing an RA to add an address then
    immediately fail DAD, we simply don't allow the address to be
    added in the first place. This also lets the user set this flag
    and disable all IPv6 addresses on the interface, or on the entire
    system.

    Signed-off-by: Brian Haley
    Signed-off-by: David S. Miller

    Brian Haley
     

15 Mar, 2009

1 commit


05 Mar, 2009

1 commit


04 Mar, 2009

1 commit

  • Add "disable" module parameter support to ipv6.ko by specifying
    "disable=1" on module load. We just do the minimum of initializing
    inetsw6[] so calls from other modules to inet6_register_protosw()
    won't OOPs, then bail out. No IPv6 addresses or sockets can be
    created as a result, and a reboot is required to enable IPv6.

    Signed-off-by: Brian Haley
    Signed-off-by: David S. Miller

    Brian Haley
     

27 Feb, 2009

1 commit

  • This file documents the specifics of the RDS sockets API,
    as well as covering some of the details of its internal
    implementation.

    Signed-off-by: Andy Grover
    Signed-off-by: David S. Miller

    Andy Grover
     

24 Feb, 2009

2 commits


23 Feb, 2009

1 commit

  • Extend existing reverse path filter option to allow strict or loose
    filtering. (See http://en.wikipedia.org/wiki/Reverse_path_filtering).

    For compatibility with existing usage, the value 1 is chosen for strict mode
    and 2 for loose mode.

    Signed-off-by: Stephen Hemminger
    Signed-off-by: David S. Miller

    Stephen Hemminger
     

16 Feb, 2009

2 commits

  • Instructions for time stamping outgoing packets are take from the
    socket layer and later copied into the new skb.

    Signed-off-by: Patrick Ohly
    Signed-off-by: David S. Miller

    Patrick Ohly
     
  • User space can request hardware and/or software time stamping.
    Reporting of the result(s) via a new control message is enabled
    separately for each field in the message because some of the
    fields may require additional computation and thus cause overhead.
    User space can tell the different kinds of time stamps apart
    and choose what suits its needs.

    When a TX timestamp operation is requested, the TX skb will be cloned
    and the clone will be time stamped (in hardware or software) and added
    to the socket error queue of the skb, if the skb has a socket
    associated with it.

    The actual TX timestamp will reach userspace as a RX timestamp on the
    cloned packet. If timestamping is requested and no timestamping is
    done in the device driver (potentially this may use hardware
    timestamping), it will be done in software after the device's
    start_hard_xmit routine.

    Signed-off-by: Patrick Ohly
    Signed-off-by: David S. Miller

    Patrick Ohly
     

01 Feb, 2009

1 commit


31 Jan, 2009

1 commit


30 Jan, 2009

1 commit


27 Jan, 2009

2 commits


22 Jan, 2009

1 commit

  • This adds full support for local/remote Sequence Window feature, from which the
    * sequence-number-validity (W) and
    * acknowledgment-number-validity (W') windows
    derive as specified in RFC 4340, 7.5.3.

    Specifically, the following is contained in this patch:
    * integrated new socket fields into dccp_sk;
    * updated the update_gsr/gss routines with regard to these fields;
    * updated handler code: the Sequence Window feature is located at the TX side,
    so the local feature is meant if the handler-rx flag is false;
    * the initialisation of `rcv_wnd' in reqsk is removed, since
    - rcv_wnd is not used by the code anywhere;
    - sequence number checks are not done in the LISTEN state (cf. 7.5.3);
    - dccp_check_req checks the Ack number validity more rigorously;
    * the `struct dccp_minisock' became empty and is now removed.

    Signed-off-by: Gerrit Renker
    Acked-by: Ian McDonald
    Signed-off-by: David S. Miller

    Gerrit Renker
     

06 Jan, 2009

1 commit