Re: KLive: Linux Kernel Live Usage Monitor

From: Andrea Arcangeli (andrea_at_suse.de)
Date: 08/31/05

  • Next message: Chris Clayton: "2.6.13 - strange usb keyboard behaviour"
    Date:	Wed, 31 Aug 2005 21:47:01 +0200
    To: tony.luck@intel.com
    
    

    On Wed, Aug 31, 2005 at 12:14:23PM -0700, tony.luck@intel.com wrote:
    > Do you want to try to handle version skew ? All kernels built
    > from GIT trees look like 2.6.13 until Linus releases 2.6.14-rc1.
    > Possible approaches (requiring changes to the kernel Makefile).
    > 1) Use the SHA1 of HEAD to provide a precise identification.
    > 2) Use $(git-rev-tree linus ^v${VERSION}.${PATCHLEVEL}.${SUBLEVEL}${EXTRAVERSION} | wc -l)
    > to get an approximate distance from the base version
    >
    > Another version issue is use of "localversion" ... I use it to tag
    > kernels with a summary of the config file I used during build (e.g.
    > -tiger-smp, or -generic-up). Looking at the results you've collected
    > so far, there appear to be a variety of other conventions in use
    > that prevent aggregation of results.

    Aggregation of results seems the biggest problem right now. If we add
    the git tag we really have to aggregate the git revisions before showing
    the main page (or there would be too many of them). So we need at least
    a standard way to do that. Perhaps it's simpler to export it via
    readonly sysctl or with /proc and passed separately to the server (not
    mixed in the uname strings)? I can extend the protocol without
    invalidating the old clients and old data.

    I'm thinking to add optional aggregations for (\d+)\.(\d+)\.(\d+)\D and
    for different archs. So you can watch ia64 only or 2.6.13 only etc...

    The "-tiger-smp/-generic-up" makes life harder indeed ;).

    If there was a more standard way to add extraversions and localversions
    aggregation would be easier and more reliable.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Chris Clayton: "2.6.13 - strange usb keyboard behaviour"

    Relevant Pages

    • [Bug 973] Presario laptop panic on boot
      ... using "standard" kernels or -mm kernels. ... In "standard" kernels I have occasionally seen an oops in the synaptics ... or because it is harder to trigger. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.
      ... the Debian stance is that the kernel proper ... It merely depends on the definition of "aggregation". ... This is not the case for a binary kernel module, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: time dimension help!
      ... like there may be some scope for replacing custom rollups with standard ... aggregation functions. ... then using standard aggregation on those should speed up ... Deepak Puri ...
      (microsoft.public.sqlserver.olap)
    • Re: Multiple aggregated links between devices impossible?
      ... between Cisco devices, but only one 802.3ad aggregation is possible if ... That the standard only requires one between different vendors. ... proprietary aggregation mechanism before LACP. ...
      (comp.dcom.lans.ethernet)