1. 21 3月, 2006 1 次提交
    • S
      [NET] core: add RFC2863 operstate · b00055aa
      Stefan Rompf 提交于
      this patch adds a dormant flag to network devices, RFC2863 operstate derived
      from these flags and possibility for userspace interaction. It allows drivers
      to signal that a device is unusable for user traffic without disabling
      queueing (and therefore the possibility for protocol establishment traffic to
      flow) and a userspace supplicant (WPA, 802.1X) to mark a device unusable
      without changes to the driver.
      
      It is the result of our long discussion. However I must admit that it
      represents what Jamal and I agreed on with compromises towards Krzysztof, but
      Thomas and Krzysztof still disagree with some parts. Anyway I think it should
      be applied.
      Signed-off-by: NStefan Rompf <stefan@loplof.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b00055aa
  2. 20 12月, 2005 1 次提交
  3. 30 8月, 2005 1 次提交
  4. 29 6月, 2005 2 次提交
  5. 24 6月, 2005 1 次提交
  6. 19 6月, 2005 4 次提交
    • T
      8f48bcd4
    • T
      [NETLINK]: Fix RTA_NEST_CANCEL(). · c52a3f89
      Thomas Graf 提交于
      Only skb_trim() if 'start' is non-NULL.
      Signed-off-by: NThomas Graf <tgraf@suug.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c52a3f89
    • T
      [NETLINK]: Neighbour table configuration and statistics via rtnetlink · c7fb64db
      Thomas Graf 提交于
      To retrieve the neighbour tables send RTM_GETNEIGHTBL with the
      NLM_F_DUMP flag set. Every neighbour table configuration is
      spread over multiple messages to avoid running into message
      size limits on systems with many interfaces. The first message
      in the sequence transports all not device specific data such as
      statistics, configuration, and the default parameter set.
      This message is followed by 0..n messages carrying device
      specific parameter sets.
      
      Although the ordering should be sufficient, NDTA_NAME can be
      used to identify sequences. The initial message can be identified
      by checking for NDTA_CONFIG. The device specific messages do
      not contain this TLV but have NDTPA_IFINDEX set to the
      corresponding interface index.
      
      To change neighbour table attributes, send RTM_SETNEIGHTBL
      with NDTA_NAME set. Changeable attribute include NDTA_THRESH[1-3],
      NDTA_GC_INTERVAL, and all TLVs in NDTA_PARMS unless marked
      otherwise. Device specific parameter sets can be changed by
      setting NDTPA_IFINDEX to the interface index of the corresponding
      device.
      Signed-off-by: NThomas Graf <tgraf@suug.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c7fb64db
    • T
      [NETLINK] Routing attribute related shortcuts · 00768244
      Thomas Graf 提交于
       RTA_GET_U(32|64)(tlv)
         Assumes TLV is a u32/u64 field and returns its value.
      
       RTA_GET_[M]SECS(tlv)
         Assumes TLV is a u64 and transports jiffies converted
         to seconds or milliseconds and returns its value.
      
       RTA_PUT_U(32|64)(skb, type, value)
         Appends %value as fixed u32/u64 to %skb as TLV %type.
      
       RTA_PUT_[M]SECS(skb, type, jiffies)
         Converts %jiffies to secs/msecs and appends it as u64
         to %skb as TLV %type.
      
       RTA_PUT_STRING(skb, type, string)
         Appends %NUL terminated %string to %skb as TLV %type.
      
       RTA_NEST(skb, type)
         Starts a nested TLV %type and returns the nesting handle.
      
       RTA_NEST_END(skb, nesting_handle)
         Finishes the nested TLV %nesting_handle, must be called
         symmetric to RTA_NEST(). Returns skb->len
      
       RTA_NEST_CANCEL(skb, nesting_handle)
         Cancel the nested TLV %nesting_handle and trim nested TLV
         from skb again, returns -1.
      Signed-off-by: NThomas Graf <tgraf@suug.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      00768244
  7. 04 5月, 2005 3 次提交
  8. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4