ru.unix.bsd

 
 - RU.UNIX.BSD ------------------------------------------------------------------
 From : Slawa Olhovchenkov                   2:5030/500     18 Aug 2004  23:07:50
 To : All
 Subject : Вести с полей
 -------------------------------------------------------------------------------- 
 

 
 А тем временем в замке шефа...
 
 From: Colin Percival <colin.percival@wadham.ox.ac.uk>
 Subject: Enhanced SpeedStep driver available
 
   Thanks to everyone who has been sending me data about their
 processors (and in particular, the 90nm versions), I now have
 a first draft of a Enhanced SpeedStep driver available.  For
 people with the appropriate processors (Pentium M only), this
 makes it possible to adjust the cpu frequency via a new sysctl
 (hw.est_curfreq), and have the cpu voltage adjusted at the
 same time.
   I've also put together a very simple control daemon which
 reads kern.cp_time every second and adjusts the cpu frequency
 based on the fraction of cpu time which is idle.  This increases
 my laptop's battery life by around 40%.
   All the code is online at
 http://www.daemonology.net/freebsd-est/
   Assuming I don't hear any major bug reports in the next few
 days, I'll package these into ports and hopefully get them into
 the ports tree in time for 5.3-RELEASE.
 
 Colin Percival
 
 I found ACPI driver here:
 http://www.spa.is.uec.ac.jp/~nfukuda/software/
 
 FYI...
 
 Jung-uk Kim
 
 andre       2004-08-17 22:05:54 UTC
 
   FreeBSD src repository
 
   Modified files:
     sys/conf             files options
     sys/modules/ipfw     Makefile
     sys/net              bridge.c
     sys/netgraph         ng_bridge.c
     sys/netinet          ip_divert.c ip_dummynet.c ip_dummynet.h
                          ip_fastfwd.c ip_fw.h ip_fw2.c ip_input.c
                          ip_output.c ip_var.h raw_ip.c tcp_input.c
                          tcp_sack.c
     sys/sys              mbuf.h
   Added files:
     sys/netinet          ip_fw_pfil.c
   Log:
   Convert ipfw to use PFIL_HOOKS.  This is change is transparent to userland
   and preserves the ipfw ABI.  The ipfw core packet inspection and filtering
   functions have not been changed, only how ipfw is invoked is different.
 
   However there are many changes how ipfw is and its add-on's are handled:
 
    In general ipfw is now called through the PFIL_HOOKS and most associated
    magic, that was in ip_input() or ip_output() previously, is now done in
    ipfw_check_[in|out]() in the ipfw PFIL handler.
 
    IPDIVERT is entirely handled within the ipfw PFIL handlers.  A packet to
    be diverted is checked if it is fragmented, if yes, ip_reass() gets in for
    reassembly.  If not, or all fragments arrived and the packet is complete,
    divert_packet is called directly.  For 'tee' no reassembly attempt is made
    and a copy of the packet is sent to the divert socket unmodified.  The
    original packet continues its way through ip_input/output().
 
    ipfw 'forward' is done via m_tag's.  The ipfw PFIL handlers tag the packet
    with the new destination sockaddr_in.  A check if the new destination is a
    local IP address is made and the m_flags are set appropriately.  ip_input()
    and ip_output() have some more work to do here.  For ip_input() the m_flags
    are checked and a packet for us is directly sent to the 'ours' section for
    further processing.  Destination changes on the input path are only tagged
    and the 'srcrt' flag to ip_forward() is set to disable destination checks
    and ICMP replies at this stage.  The tag is going to be handled on output.
    ip_output() again checks for m_flags and the 'ours' tag.  If found, the
    packet will be dropped back to the IP netisr where it is going to be picked
    up by ip_input() again and the directly sent to the 'ours' section.  When
    only the destination changes, the route's 'dst' is overwritten with the
    new destination from the forward m_tag.  Then it jumps back at the route
    lookup again and skips the firewall check because it has been marked with
    M_SKIP_FIREWALL.  ipfw 'forward' has to be compiled into the kernel with
    'option IPFIREWALL_FORWARD' to enable it.
 
    DUMMYNET is entirely handled within the ipfw PFIL handlers.  A packet for
    a dummynet pipe or queue is directly sent to dummynet_io().  Dummynet will
    then inject it back into ip_input/ip_output() after it has served its time.
    Dummynet packets are tagged and will continue from the next rule when they
    hit the ipfw PFIL handlers again after re-injection.
 
    BRIDGING and IPFW_ETHER are not changed yet and use ipfw_chk() directly as
    they did before.  Later this will be changed to dedicated ETHER PFIL_HOOKS.
 ... Hо ведь всех говорунов истребили. Ведь так?
 --- GoldED+/BSD 1.1.5
  * Origin:  (2:5030/500)
 
 

Вернуться к списку тем, сортированных по: возрастание даты  уменьшение даты  тема  автор