* [PATCH 2/11] perfmon2 patch for review: modified generic files
From: Stephane Eranian @ 2006-05-12 16:33 UTC (permalink / raw)
To: linux-kernel; +Cc: eranian
This patch contains all the modified generic files.
diff -ur --exclude-from=/tmp/excl37102 linux-2.6.17-rc4.orig/Makefile linux-2.6.17-rc4/Makefile
--- linux-2.6.17-rc4.orig/Makefile 2006-05-12 03:16:09.000000000 -0700
+++ linux-2.6.17-rc4/Makefile 2006-05-12 03:19:19.000000000 -0700
@@ -1,7 +1,7 @@
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 17
-EXTRAVERSION =-rc4
+EXTRAVERSION =-rc4-perfmon2
NAME=Sliding Snow Leopard
# *DOCUMENTATION*
@@ -518,7 +518,7 @@
ifeq ($(KBUILD_EXTMOD),)
-core-y += kernel/ mm/ fs/ ipc/ security/ crypto/ block/
+core-y += kernel/ mm/ fs/ ipc/ security/ crypto/ block/ perfmon/
vmlinux-dirs := $(patsubst %/,%,$(filter %/, $(init-y) $(init-m) \
$(core-y) $(core-m) $(drivers-y) $(drivers-m) \
diff -ur --exclude-from=/tmp/excl37102 linux-2.6.17-rc4.orig/include/linux/sched.h linux-2.6.17-rc4/include/linux/sched.h
--- linux-2.6.17-rc4.orig/include/linux/sched.h 2006-05-12 03:16:14.000000000 -0700
+++ linux-2.6.17-rc4/include/linux/sched.h 2006-05-12 03:18:52.000000000 -0700
@@ -40,6 +40,7 @@
#include <linux/auxvec.h> /* For AT_VECTOR_SIZE */
struct exec_domain;
+struct pfm_context;
/*
* cloning flags:
@@ -888,6 +889,10 @@
* cache last used pipe for splice
*/
struct pipe_inode_info *splice_pipe;
+
+#ifdef CONFIG_PERFMON
+ struct pfm_context *pfm_context;
+#endif
};
static inline pid_t process_group(struct task_struct *tsk)
diff -ur --exclude-from=/tmp/excl37102 linux-2.6.17-rc4.orig/include/linux/syscalls.h linux-2.6.17-rc4/include/linux/syscalls.h
--- linux-2.6.17-rc4.orig/include/linux/syscalls.h 2006-05-12 03:16:14.000000000 -0700
+++ linux-2.6.17-rc4/include/linux/syscalls.h 2006-05-12 03:18:52.000000000 -0700
@@ -29,6 +29,13 @@
struct new_utsname;
struct nfsctl_arg;
struct __old_kernel_stat;
+struct pfarg_ctx;
+struct pfarg_pmc;
+struct pfarg_pmd;
+struct pfarg_start;
+struct pfarg_load;
+struct pfarg_setinfo;
+struct pfarg_setdesc;
struct pollfd;
struct rlimit;
struct rusage;
@@ -582,4 +589,27 @@
asmlinkage long sys_sync_file_range(int fd, loff_t offset, loff_t nbytes,
unsigned int flags);
+asmlinkage long sys_pfm_create_context(struct pfarg_ctx __user *ureq,
+ void __user *uarg, size_t smpl_size);
+asmlinkage long sys_pfm_write_pmcs(int fd, struct pfarg_pmc __user *ureq,
+ int count);
+asmlinkage long sys_pfm_write_pmds(int fd, struct pfarg_pmd __user *ureq,
+ int count);
+asmlinkage long sys_pfm_read_pmds(int fd, struct pfarg_pmd __user *ureq,
+ int count);
+asmlinkage long sys_pfm_restart(int fd);
+asmlinkage long sys_pfm_stop(int fd);
+asmlinkage long sys_pfm_start(int fd, struct pfarg_start __user *ureq);
+asmlinkage long sys_pfm_load_context(int fd, struct pfarg_load __user *ureq);
+asmlinkage long sys_pfm_unload_context(int fd);
+asmlinkage long sys_pfm_delete_evtsets(int fd,
+ struct pfarg_setinfo __user *ureq,
+ int count);
+asmlinkage long sys_pfm_create_evtsets(int fd,
+ struct pfarg_setdesc __user *ureq,
+ int count);
+asmlinkage long sys_pfm_getinfo_evtsets(int fd,
+ struct pfarg_setinfo __user *ureq,
+ int count);
+
#endif
diff -ur --exclude-from=/tmp/excl37102 linux-2.6.17-rc4.orig/kernel/sched.c linux-2.6.17-rc4/kernel/sched.c
--- linux-2.6.17-rc4.orig/kernel/sched.c 2006-05-12 03:16:14.000000000 -0700
+++ linux-2.6.17-rc4/kernel/sched.c 2006-05-12 03:18:52.000000000 -0700
@@ -50,6 +50,7 @@
#include <linux/times.h>
#include <linux/acct.h>
#include <linux/kprobes.h>
+#include <linux/perfmon.h>
#include <asm/tlb.h>
#include <asm/unistd.h>
diff -ur --exclude-from=/tmp/excl37102 linux-2.6.17-rc4.orig/kernel/sys_ni.c linux-2.6.17-rc4/kernel/sys_ni.c
--- linux-2.6.17-rc4.orig/kernel/sys_ni.c 2006-05-12 03:16:14.000000000 -0700
+++ linux-2.6.17-rc4/kernel/sys_ni.c 2006-05-12 03:18:52.000000000 -0700
@@ -111,6 +111,19 @@
cond_syscall(compat_sys_ipc);
cond_syscall(compat_sys_sysctl);
+cond_syscall(sys_pfm_create_context);
+cond_syscall(sys_pfm_write_pmcs);
+cond_syscall(sys_pfm_write_pmds);
+cond_syscall(sys_pfm_read_pmds);
+cond_syscall(sys_pfm_restart);
+cond_syscall(sys_pfm_start);
+cond_syscall(sys_pfm_stop);
+cond_syscall(sys_pfm_load_context);
+cond_syscall(sys_pfm_unload_context);
+cond_syscall(sys_pfm_create_evtsets);
+cond_syscall(sys_pfm_delete_evtsets);
+cond_syscall(sys_pfm_getinfo_evtsets);
+
/* arch-specific weak syscall entries */
cond_syscall(sys_pciconfig_read);
cond_syscall(sys_pciconfig_write);
diff -ur --exclude-from=/tmp/excl37102 linux-2.6.17-rc4.orig/lib/Makefile linux-2.6.17-rc4/lib/Makefile
--- linux-2.6.17-rc4.orig/lib/Makefile 2006-05-12 03:16:14.000000000 -0700
+++ linux-2.6.17-rc4/lib/Makefile 2006-05-12 03:18:52.000000000 -0700
@@ -5,7 +5,7 @@
lib-y := errno.o ctype.o string.o vsprintf.o cmdline.o \
bust_spinlocks.o rbtree.o radix-tree.o dump_stack.o \
idr.o div64.o int_sqrt.o bitmap.o extable.o prio_tree.o \
- sha1.o
+ sha1.o carta_random32.o
lib-$(CONFIG_SMP) += cpumask.o
^ permalink raw reply
* Re: [PATCH] ethtool always report port is TP on tg3
From: Michael Chan @ 2006-05-12 14:59 UTC (permalink / raw)
To: Karsten Keil; +Cc: netdev, Andrew Morton
In-Reply-To: <20060512100541.GA10529@pingi.kke.suse.de>
On Fri, 2006-05-12 at 12:05 +0200, Karsten Keil wrote:
> Even with fiber cards ethtool reports that the connected port is TP,
> the patch fix this.
ACK. Thanks. Please add sign-off line and send to DaveM.
^ permalink raw reply
* Re: 3c59x vortex_timer rt hack (was: rt20 patch question)
From: Steven Rostedt @ 2006-05-12 16:38 UTC (permalink / raw)
To: Andrew Morton; +Cc: mingo, markh, linux-kernel, dwalker, tglx
In-Reply-To: <20060512092709.5b9efab7.akpm@osdl.org>
On Fri, 12 May 2006, Andrew Morton wrote:
> Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Fri, 12 May 2006, Andrew Morton wrote:
> >
> > > >
> > > > The vortex_timer is a timeout,
> > >
> > > err, it's actually a function.
> >
> > OK, I meant vp->timer
>
> That's a kernel timer.
:P
>
> > >
> > > > will it go off often?
> > >
> > > Every five seconds if the cable's unplugged. Every 60 seconds otherwise.
> > >
> >
> > OK, so the function is a service and not a fixup (or both). Hmm, so
> > latency is an issue.
>
> yup. It's been five years, sorry - I'm struggling to remember why
> vortex_timer() needs to block the interrupt handler.
>
> The chip is fairly stateful - that EL3WINDOW() thing selects a particular
> register bank and needs protection against other register readers. But we
> should avoid running EL3WINDOW() in the rx and tx interrupt handlers anyway
> - iirc the chip is designed to permit that.
>
> Is tricky.
>
> How come -rt cannot permit disable_irq() in there?
It's about having threaded interrupts soft and hard, and their
combinations. disable_irq with threaded hardirqs can schedule, but we
still don't want a softirq to do so (when not threaded).
So it too is tricky.
>
> (I think the _reason_ it's disable_irq() is, yes, because it's infrequent
> and because it can hold off interrupts for a long time if we use
> spin_lock_irq())
>
Well, it seems that the spin_lock_irq for -rt is the answer for now, until
we sort out the dependencies of threaded interrupts.
Ingo,
Maybe it will be necessary to make hardirq threading dependent on softirq
threading.
Is it really that bad? When would someone want Hardirq threading without
having softirq threading??
-- Steve
^ permalink raw reply
* [ALSA - utils 0002116]: no sound in kernel 2.6.16-1-686
From: bugtrack @ 2006-05-12 16:37 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2116>
======================================================================
Reported By: mramirez
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 2116
Category: speakertest
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 05-12-2006 01:07 CEST
Last Modified: 05-12-2006 18:37 CEST
======================================================================
Summary: no sound in kernel 2.6.16-1-686
Description:
I have updated my kernel from 2.6.15-1-486 to 2.6.16-1-686, and now the
sound not work.
I run alsaconf, but not solve the problem.
if i boot on kernel 2.6.15-1-486 the sound work. (only in this version)
somebody help me?
======================================================================
----------------------------------------------------------------------
mramirez - 05-12-06 18:34
----------------------------------------------------------------------
i try this but the sound don't work
----------------------------------------------------------------------
tiwai - 05-12-06 18:37
----------------------------------------------------------------------
Then how about to begin with more detailed descriptions of your hardware
and problems?
Issue History
Date Modified Username Field Change
======================================================================
05-12-06 01:07 mramirez New Issue
05-12-06 16:07 tiwai Note Added: 0009777
05-12-06 18:34 mramirez Note Added: 0009785
05-12-06 18:37 tiwai Note Added: 0009787
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
^ permalink raw reply
* Re: [LARTC] HTB at 100+ Mbits/sec
From: Larry Brigman @ 2006-05-12 16:36 UTC (permalink / raw)
To: lartc
In-Reply-To: <d5c845ac0605101239r384bd499r58cc6f4571e7136b@mail.gmail.com>
On 5/12/06, Muthukumar S <muthukumar@gmail.com> wrote:
> > Iperf has a demonstrated behavior that when running more than one copy at the
> > same time on the same box (client side); that the timing of each will
> > start to effect
> > the other copies. This is a function of how Iperf does it's timing
> > (spin loops).
>
> What traffic generators would you recommend? What do other members
> use? Has anyone used TG (http://www.postel.org/tg/)?
>
I have looked at TG but would recommend D-ITG
(http://www.grid.unina.it/software/ITG/) at this point as it seems to
have more work recently. That said I have downloaded TG but have not
ran it too much.
Back to Iperf. The reason I mention the timing issue is, really only
an issue when you are running multiple copies and you really want very
stable inter-packet timing. If you want
to use Iperf for bandwidth testing and want to run multiple copies.
Get the source and find
the client send routines where it is using the delay function and
replace that with usleep.
This change allows (in my testing) upwards of 15 copies of Iperf
running at the same time
without major interactions.
For a single stream Iperf is the most flexible program of the bunch
Just for info, here is a site that has both monitoring (mostly) tools
and traffic generation tools.
http://www.slac.stanford.edu/xorg/nmtf/nmtf-tools.html
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
^ permalink raw reply
* Re: [PATCH] mtd: Trivial typo fixes
From: David Woodhouse @ 2006-05-12 16:35 UTC (permalink / raw)
To: Egry Gábor; +Cc: trivial-list, linux-kernel
In-Reply-To: <1147439088.27820.27.camel@spirit>
On Fri, 2006-05-12 at 15:04 +0200, Egry Gábor wrote:
>
> Trivial typo fixes in Kconfig files (MTD).
>
> Signed-off-by: Egry Gabor <gaboregry@t-online.hu>
Applied; thanks.
--
dwmw2
^ permalink raw reply
* [ALSA - driver 0002106]: Sound card snd-hda-intel emits NO sound
From: bugtrack @ 2006-05-12 16:34 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2106>
======================================================================
Reported By: louisvd
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 2106
Category: PCI - hda-intel
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: Fedora Core 5
Kernel Version: 2.6.16-1.2111_FC5smp
======================================================================
Date Submitted: 05-08-2006 21:00 CEST
Last Modified: 05-12-2006 18:34 CEST
======================================================================
Summary: Sound card snd-hda-intel emits NO sound
Description:
Hi
I was merrily running Fedora Core 4 and after upgrading the kernel to
2.6.16 my sound no longer worked under Linux (it works under Windows).
After a lot of battling I figured I may as well upgrade to FC5 now. A
clean install, out of the box, and the sound STILL did not work. I've
applied every available patch to date and no luck. Tonight I installed
the Alsa 1.0.11 driver, lib and util tarballs -- all installed
successfully -- but there is STILL no sound produced.
Everything LOOKS normal. There are no errors that I can detect. In the X
and console versions of Alsamixer I have ALL the devices displayed and
unmuted with the volumes at max. I've removed the sound lines from
modprobe.conf and am running with alsasound and that didn't help either --
even though it says the driver has been loaded.
FYI, the OSS Volume control calls it a Realtek ALC260. lspci refers to it
as Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller
(rev 01).
Please help.
======================================================================
----------------------------------------------------------------------
louisvd - 05-12-06 17:58
----------------------------------------------------------------------
SUCCESS!!
I changed the model to 'basic' and that worked.
Here is my modprobe.conf
alias eth0 tg3
alias scsi_hostadapter ata_piix
alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0 model=basic
remove snd-hda-intel { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
/sbin/modprobe -r --ignore-remove snd-hda-intel
Thank you VERY MUCH for your assistance. You may close this call.
----------------------------------------------------------------------
tiwai - 05-12-06 18:34
----------------------------------------------------------------------
Hm, your device is listed to the model "hp", but it looks like that the
model hp doesn't work properly as expected. So, the case isn't closed
yet.
Could you check whether the uploaded patch fixes the problem (please
remove model option if you test)?
Issue History
Date Modified Username Field Change
======================================================================
05-08-06 21:00 louisvd New Issue
05-08-06 21:00 louisvd Distribution => Fedora Core 5
05-08-06 21:00 louisvd Kernel Version => 2.6.16-1.2111_FC5smp
05-10-06 16:16 tiwai Note Added: 0009722
05-10-06 16:52 louisvd Note Added: 0009731
05-10-06 16:55 tiwai Note Added: 0009732
05-10-06 20:02 louisvd Note Added: 0009751
05-12-06 00:40 louisvd Note Added: 0009770
05-12-06 10:31 UMMO Issue Monitored: UMMO
05-12-06 16:11 tiwai Note Added: 0009778
05-12-06 17:18 louisvd Note Added: 0009782
05-12-06 17:36 tiwai Note Added: 0009783
05-12-06 17:54 UMMO Issue End Monitor: UMMO
05-12-06 17:58 louisvd Note Added: 0009784
05-12-06 18:34 tiwai Note Added: 0009786
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
^ permalink raw reply
* [ALSA - utils 0002116]: no sound in kernel 2.6.16-1-686
From: bugtrack @ 2006-05-12 16:34 UTC (permalink / raw)
To: alsa-devel
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2116>
======================================================================
Reported By: mramirez
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 2116
Category: speakertest
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 05-12-2006 01:07 CEST
Last Modified: 05-12-2006 18:34 CEST
======================================================================
Summary: no sound in kernel 2.6.16-1-686
Description:
I have updated my kernel from 2.6.15-1-486 to 2.6.16-1-686, and now the
sound not work.
I run alsaconf, but not solve the problem.
if i boot on kernel 2.6.15-1-486 the sound work. (only in this version)
somebody help me?
======================================================================
----------------------------------------------------------------------
tiwai - 05-12-06 16:07
----------------------------------------------------------------------
Try 2.6.17rc4.
----------------------------------------------------------------------
mramirez - 05-12-06 18:34
----------------------------------------------------------------------
i try this but the sound don't work
Issue History
Date Modified Username Field Change
======================================================================
05-12-06 01:07 mramirez New Issue
05-12-06 16:07 tiwai Note Added: 0009777
05-12-06 18:34 mramirez Note Added: 0009785
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
^ permalink raw reply
* Re: + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree
From: John Kelly @ 2006-05-12 16:31 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <Pine.LNX.4.58.0605121222070.5579@gandalf.stny.rr.com>
On Fri, 12 May 2006 12:24:40 -0400 (EDT), Steven Rostedt
<rostedt@goodmis.org> wrote:
>> >Sorry for falling in late but we can't do that.
>> >Win 98 (95 too?) shared can not be mounted with CIFS, it requires SMBFS.
>> W98? He's dead, Jim.
>huh, my wife has a laptop that she still uses that has w98 on it. And I do
>use smbfs to sometimes communicate with it.
Users who need vintage features can use vintage kernels. They haven't
been pulled off the market.
>Why upgrade when you don't have to?
Why drag around old worn out baggage in new kernels?
^ permalink raw reply
* Re: [linux-lvm] Can't reduce lvm2 volume. I get "Volume group mapper doesn't exist"
From: Luca Berra @ 2006-05-12 16:25 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <1147450728.8248.127.camel@morpheus.ucc.ie>
On Fri, May 12, 2006 at 05:18:48PM +0100, Marcus Claesson wrote:
>I want to shrink /dev/mapper/Volume00-LogVol02 from 97G to 20G, and this
>is what I tried.
>
the lv is called /dev/Volume00/LogVol02
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
^ permalink raw reply
* Re: [Xenomai-help] starnge latencies with native
From: Gilles Chanteperdrix @ 2006-05-12 16:25 UTC (permalink / raw)
To: Daniel Simon; +Cc: Xenomai-help
In-Reply-To: <20060512172456.555caf51@domain.hid>
Daniel Simon wrote:
> Hi all,
>
> I'm doing some tests with the native skins. The attached program uses
> an alarm to trigger a periodic task and measures the sampling latency.
>
> Initial latencies are in the range of tens of millisecs. and then
> decrease slowly to the range of microsecs:
>
> rt_timer_set_mode(TM_ONESHOT) started
> alarm started with period 1000000000 ns
> increment 1124642266 absjitter 124642266
> increment 937743828 absjitter 62256172
> increment 1031095424 absjitter 31095424
> increment 984466651 absjitter 15533349
> increment 1007758686 absjitter 7758686
> increment 996126407 absjitter 3873593
> increment 1001934707 absjitter 1934707
> increment 999039749 absjitter 960251
> increment 1000477139 absjitter 477139
> increment 999759707 absjitter 240293
> increment 1000119631 absjitter 119631
> increment 999938964 absjitter 61036
> increment 1000029816 absjitter 29816
> increment 999985508 absjitter 14492
> increment 1000004750 absjitter 4750
> increment 999998882 absjitter 1118
> increment 1000000946 absjitter 946
> increment 999998780 absjitter 1220
> increment 1000001951 absjitter 1951
> increment 999999514 absjitter 486
> increment 999998746 absjitter 1254
> [...]
>
> What may be wrong?
Are you still running a kernel with ACPI_PROCESSOR ?
--
Gilles Chanteperdrix.
^ permalink raw reply
* Re: 3c59x vortex_timer rt hack (was: rt20 patch question)
From: Andrew Morton @ 2006-05-12 16:27 UTC (permalink / raw)
To: Steven Rostedt; +Cc: mingo, markh, linux-kernel, dwalker, tglx
In-Reply-To: <Pine.LNX.4.58.0605121208350.5357@gandalf.stny.rr.com>
Steven Rostedt <rostedt@goodmis.org> wrote:
>
>
>
> On Fri, 12 May 2006, Andrew Morton wrote:
>
> > >
> > > The vortex_timer is a timeout,
> >
> > err, it's actually a function.
>
> OK, I meant vp->timer
That's a kernel timer.
> >
> > > will it go off often?
> >
> > Every five seconds if the cable's unplugged. Every 60 seconds otherwise.
> >
>
> OK, so the function is a service and not a fixup (or both). Hmm, so
> latency is an issue.
yup. It's been five years, sorry - I'm struggling to remember why
vortex_timer() needs to block the interrupt handler.
The chip is fairly stateful - that EL3WINDOW() thing selects a particular
register bank and needs protection against other register readers. But we
should avoid running EL3WINDOW() in the rx and tx interrupt handlers anyway
- iirc the chip is designed to permit that.
Is tricky.
How come -rt cannot permit disable_irq() in there?
(I think the _reason_ it's disable_irq() is, yes, because it's infrequent
and because it can hold off interrupts for a long time if we use
spin_lock_irq())
^ permalink raw reply
* Re: + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree
From: Steven Rostedt @ 2006-05-12 16:24 UTC (permalink / raw)
To: John Kelly; +Cc: linux-kernel
In-Reply-To: <200605121619.k4CGJCtR004972@isp2dial.com>
On Fri, 12 May 2006, John Kelly wrote:
> On Fri, 12 May 2006 17:03:56 +0200 (MEST), Jan Engelhardt
> <jengelh@linux01.gwdg.de> wrote:
>
> >> > smbfs is a bit buggy and has no maintainer. Change it to shout at the user on
> >> > the first five mount attempts - tell them to switch to CIFS.
>
> >> > Come November we'll mark it BROKEN and see what happens.
>
> >Sorry for falling in late but we can't do that.
> >Win 98 (95 too?) shared can not be mounted with CIFS, it requires SMBFS.
>
> W98? He's dead, Jim.
>
huh, my wife has a laptop that she still uses that has w98 on it. And I do
use smbfs to sometimes communicate with it. Why upgrade when you don't
have to?
-- Steve
^ permalink raw reply
* RE: SOAP
From: Ratin Rahman (mratin) @ 2006-05-12 16:24 UTC (permalink / raw)
To: Ralf Roesch; +Cc: linux-mips
Thanks, good to know about the illegal XML serialization patent that
Microsoft obtained from the patent office on that page.
Ratin
-----Original Message-----
From: Ralf Roesch [mailto:ralf.roesch@rw-gmbh.de]
Sent: Friday, May 12, 2006 12:51 AM
To: Ratin
Cc: linux-mips@linux-mips.org
Subject: Re: SOAP
we have successfully used gSOAP since years now on a mips based embedded
target runing linux from mips-org.
Further related information about the gSOAP project you can find at
http://www.cs.fsu.edu/~engelen/soap.html
Ralf
Roesch & Walter___________________________________________
Industrie-Elektronik GmbH * Tel.: +49-7824 / 6628-0
Im Heidenwinkel 5 * Fax: +49-7824 / 6628-29
D-77963 Schwanau * mailto:ralf.roesch@rw-gmbh.de
Germany * WWW: http://www.rw-gmbh.de
Ratin wrote:
> Is there an implementation of SOAP (Simple Object Access Protocol) for
> linux-mips?
>
> Ratin
>
^ permalink raw reply
* RE: SOAP
From: Ratin Rahman (mratin) @ 2006-05-12 16:24 UTC (permalink / raw)
To: Ralf Roesch; +Cc: linux-mips
Thanks, good to know about the illegal XML serialization patent that
Microsoft obtained from the patent office on that page.
Ratin
-----Original Message-----
From: Ralf Roesch [mailto:ralf.roesch@rw-gmbh.de]
Sent: Friday, May 12, 2006 12:51 AM
To: Ratin
Cc: linux-mips@linux-mips.org
Subject: Re: SOAP
we have successfully used gSOAP since years now on a mips based embedded
target runing linux from mips-org.
Further related information about the gSOAP project you can find at
http://www.cs.fsu.edu/~engelen/soap.html
Ralf
Roesch & Walter___________________________________________
Industrie-Elektronik GmbH * Tel.: +49-7824 / 6628-0
Im Heidenwinkel 5 * Fax: +49-7824 / 6628-29
D-77963 Schwanau * mailto:ralf.roesch@rw-gmbh.de
Germany * WWW: http://www.rw-gmbh.de
Ratin wrote:
> Is there an implementation of SOAP (Simple Object Access Protocol) for
> linux-mips?
>
> Ratin
>
^ permalink raw reply
* 2.6 vs 2.4
From: Thiago Galesi @ 2006-05-12 16:24 UTC (permalink / raw)
To: Felix Domke; +Cc: linuxppc-dev
In-Reply-To: <44649F09.2020803@elitedvb.net>
> Can you point me to a list of changes which where done? I really like to
> check if they apply to my performance problems with 2.6 kernels, i.e. if
> it's worth porting the board specific changes to a newer kernel.
>
I'm sorry, I was thinking (specifically) of the 8XX port that went
from broken to maintained.
It would help if you could mention some ofthe problems you are having.
>When we switched from 2.4 to 2.6, IDE performance ("hdparm -t" to have a
>single number) was reduced by about 25% (even after trying to finetune
>the IDE driver
>On a 300MHz embedded mips machine, saturating a 100MBit network link via
>ftp is not easy.
Unfortunatelly my knowlege of IDE is almost 0. Maybe it has something
to do with schedulers being used?
About network, I had better results with a much slower processor than
your reported 5Mb/s (60MHz PPC in 2.6.10)
Thiago
^ permalink raw reply
* Re: [PATCH 13/14] FS-Cache: Release page->private in failed readahead [try #8]
From: David Howells @ 2006-05-12 16:23 UTC (permalink / raw)
To: Andrew Morton
Cc: David Howells, torvalds, steved, trond.myklebust, aviro,
linux-fsdevel, linux-cachefs, nfsv4, linux-kernel
In-Reply-To: <20060512071100.5c5d52e9.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
> > SetPageLocked(page);
>
> if (TestSetPagLocked(page))
> BUG();
>
> would make me more comfortable..
That shouldn't be necessary if add_to_page_cache() also doesn't do that, but
if you wish, I can do that - it's the error handling path, so it doesn't
matter too much performancewise.
> > > For the second hunk, is it not possible to do this cleanup in the callback
> > > function?
> >
> > Which callback function?
>
> I was referring to the filler_t thingy. Is it not possible to get control
> of that?
Well, the filler_t thing is generally a_ops->readpage from the caller fs, but
we don't want to call that if add_to_page_cache() failed, and we don't want to
call it if we're just discarding a bunch of pages we've now no intention of
actually reading.
I suppose we could add another callback for ditching pages we don't want to
keep. This has the potential to be called quite a lot because of the way
readahead works on Linux.
> So please, can we have some comments in there which describe the new
> behaviour in a manner sufficient for a maintainer to follow so people don't
> break your stuff?
Okay... I'll add more comments. I should probably also extend the
documentation on releasepage(). It won't be till Monday though.
> > Out of interest, why do we need PG_private to say there's something in
> > page->private? Can't it just be assumed either that if page->private is
> > non-zero or that if a_ops->releasepage() is non-NULL, then we need to
> > "release" the page?
>
> page->private is an unsigned long, not a pointer. The core kernel hence
> cannot determine from its value whether or not it is live. For example, the
> fs might choose to treat it as a bitmap of which-blocks-are-uptodate and
> which-blocks-are-dirty.
Then the second option is still possible (calling releasepage()
unconditionally).
David
^ permalink raw reply
* Re: [PATCH 13/14] FS-Cache: Release page->private in failed readahead [try #8]
From: David Howells @ 2006-05-12 16:23 UTC (permalink / raw)
To: Andrew Morton
Cc: aviro, linux-kernel, nfsv4, trond.myklebust, torvalds,
linux-cachefs, linux-fsdevel
In-Reply-To: <20060512071100.5c5d52e9.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
> > SetPageLocked(page);
>
> if (TestSetPagLocked(page))
> BUG();
>
> would make me more comfortable..
That shouldn't be necessary if add_to_page_cache() also doesn't do that, but
if you wish, I can do that - it's the error handling path, so it doesn't
matter too much performancewise.
> > > For the second hunk, is it not possible to do this cleanup in the callback
> > > function?
> >
> > Which callback function?
>
> I was referring to the filler_t thingy. Is it not possible to get control
> of that?
Well, the filler_t thing is generally a_ops->readpage from the caller fs, but
we don't want to call that if add_to_page_cache() failed, and we don't want to
call it if we're just discarding a bunch of pages we've now no intention of
actually reading.
I suppose we could add another callback for ditching pages we don't want to
keep. This has the potential to be called quite a lot because of the way
readahead works on Linux.
> So please, can we have some comments in there which describe the new
> behaviour in a manner sufficient for a maintainer to follow so people don't
> break your stuff?
Okay... I'll add more comments. I should probably also extend the
documentation on releasepage(). It won't be till Monday though.
> > Out of interest, why do we need PG_private to say there's something in
> > page->private? Can't it just be assumed either that if page->private is
> > non-zero or that if a_ops->releasepage() is non-NULL, then we need to
> > "release" the page?
>
> page->private is an unsigned long, not a pointer. The core kernel hence
> cannot determine from its value whether or not it is live. For example, the
> fs might choose to treat it as a bitmap of which-blocks-are-uptodate and
> which-blocks-are-dirty.
Then the second option is still possible (calling releasepage()
unconditionally).
David
^ permalink raw reply
* Re: [Qemu-devel] PATCH: Support for multi-file raw images
From: andrzej zaborowski @ 2006-05-12 16:22 UTC (permalink / raw)
To: qemu-devel
In-Reply-To: <20060512143517.GL15855@narn.hozed.org>
Hi there,
> > o If the files comprising the device are deleted (for example) while
> > QEMU is running then this is quite bad. Currently this will result
> > in read/write requests returning -1. Maybe it makes sense to panic
> > and cause QEMU to exit.
> >
>
> at the very least, the console should print an error. If you can keep
> all the files open, deleting the file won't be a problem.
>
I think 99% of the software used today assumes nobody deletes its
files while it's running and it's not a very bad assumption. QEMU is
not particularly verbose about errors in general, but if it was going
to check for a deleted file, I think it should rather report an I/O
error to the guest than print errors to the console.
Greetings,
Andrew
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
^ permalink raw reply
* Re: 2.6 for DECstation, d-i
From: Ralf Baechle @ 2006-05-12 16:20 UTC (permalink / raw)
To: Martin Michlmayr
Cc: Maciej W. Rozycki, Karel van Houten, debian-mips, linux-mips
In-Reply-To: <20060512151201.GJ7863@deprecation.cyrius.com>
On Fri, May 12, 2006 at 05:12:01PM +0200, Martin Michlmayr wrote:
> * Maciej W. Rozycki <macro@linux-mips.org> [2006-05-12 11:57]:
> > > Yeah, but the problem is that ZS is not a config option anymore. I
> > > hacked up something to see if the driver works but I guess there's a
> > > nicer solution.
> > Of course there is. Just enable SERIAL_NONSTANDARD, SERIAL_DEC,
> > SERIAL_DEC_CONSOLE and ZS. They are all in drivers/char/Kconfig and it's
> > not a coincidence the options are the same as in 2.4.
>
> Hmm, okay, they are in the linux-mips tree, but not in mainline. :/
And they won't go there just like any other drivers/char/ serial driver..
Ralf
^ permalink raw reply
* Re: + deprecate-smbfs-in-favour-of-cifs.patch added to -mm tree
From: John Kelly @ 2006-05-12 16:19 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <Pine.LNX.4.61.0605121243460.9918@yvahk01.tjqt.qr>
On Fri, 12 May 2006 17:03:56 +0200 (MEST), Jan Engelhardt
<jengelh@linux01.gwdg.de> wrote:
>> > smbfs is a bit buggy and has no maintainer. Change it to shout at the user on
>> > the first five mount attempts - tell them to switch to CIFS.
>> > Come November we'll mark it BROKEN and see what happens.
>Sorry for falling in late but we can't do that.
>Win 98 (95 too?) shared can not be mounted with CIFS, it requires SMBFS.
W98? He's dead, Jim.
^ permalink raw reply
* [linux-lvm] Can't reduce lvm2 volume. I get "Volume group mapper doesn't exist"
From: Marcus Claesson @ 2006-05-12 16:18 UTC (permalink / raw)
To: linux-lvm
Hi!
I have a problem reducing a logical volume and I'm sure it's just some
silly error, but I can't get my head around it.
I've got lvm2-2.02.01-1.3.RHEL4 installed on kernel-2.6.9-34.ELsmp.
This is what I got mounted:
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p2 49G 20G 27G 42% /
/dev/cciss/c0d0p1 99M 9.8M 84M 11% /boot
/dev/mapper/Volume00-LogVol00
97G 84G 8.1G 92% /home
none 2.9G 0 2.9G 0% /dev/shm
/dev/mapper/Volume00-LogVol02
97G 11G 81G 12% /usr/local
/dev/mapper/Volume00-LogVol01
97G 84G 8.3G 91% /var
I want to shrink /dev/mapper/Volume00-LogVol02 from 97G to 20G, and this
is what I tried.
# umount /dev/mapper/Volume00-LogVol02
# e2fsck -f /dev/mapper/Volume00-LogVol02
e2fsck 1.35 (28-Feb-2004)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/Volume00-LogVol02: 56614/12812288 files (1.5% non-
contiguous), 3099826/25600000 blocks
# resize2fs -p /dev/mapper/Volume00-LogVol02 20G
resize2fs 1.35 (28-Feb-2004)
Resizing the filesystem on /dev/mapper/Volume00-LogVol02 to 5242880 (4k)
blocks.
Begin pass 2 (max = 1787074)
Relocating blocks XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 3 (max = 782)
Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 4 (max = 2690)
Updating inode references XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXThe
filesystem on /dev/mapper/Volume00-LogVol02 is now 5242880 blocks long.
But here I get error messages:
# lvreduce -L 20G -v /dev/mapper/Volume00-LogVol02
Finding volume group mapper
Wiping cache of LVM-capable devices
Volume group mapper doesn't exist
I also tried:
# lvresize -L 20G -v /dev/mapper/Volume00-LogVol02
Finding volume group mapper
Wiping cache of LVM-capable devices
Volume group mapper doesn't exist
I then mounted the device again and saw it was 20G big. But no more
extra size had been added to the volume group...
What am I doing wrong???
Really appreciate any help!
Regards,
Marcus
^ permalink raw reply
* [PATCH] Make "xm mem-set" be lower bound on domX-min-mem
From: Puthiyaparambil, Aravindh @ 2006-05-12 16:16 UTC (permalink / raw)
To: xen-devel, Keir Fraser
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
This patch causes "xm mem-set" to be lower bound on domX-min-mem option
in xend-config. Another configuration option called domU-min-mem has
been introduced, which works similarly to dom0-min-mem. This is prevents
users from freezing the system when doing "xm mem-set" on very low
values like 32M.
Signed-off-by: Aravindh Puthiyaparambil
<aravindh.puthiyaparambil@unisys.com>
[-- Attachment #2: xend_xm-mem-set.patch --]
[-- Type: application/octet-stream, Size: 2809 bytes --]
diff -r 062d109ce872 tools/examples/xend-config.sxp
--- a/tools/examples/xend-config.sxp Thu May 11 22:39:44 2006 +0100
+++ b/tools/examples/xend-config.sxp Fri May 12 11:29:53 2006 -0400
@@ -125,6 +125,9 @@
# If dom0-cpus = 0, dom0 will take all cpus available
(dom0-cpus 0)
+# domU-min-mem works similarly to dom0-min-mem.
+(domU-min-mem 64)
+
# Whether to enable core-dumps when domains crash.
#(enable-dump no)
diff -r 062d109ce872 tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py Thu May 11 22:39:44 2006 +0100
+++ b/tools/python/xen/xend/XendDomainInfo.py Fri May 12 11:29:53 2006 -0400
@@ -101,6 +101,8 @@ RESTART_IN_PROGRESS = 'xend/restart_in_p
xc = xen.lowlevel.xc.xc()
xroot = XendRoot.instance()
+
+PRIV_DOMAIN = 0
log = logging.getLogger("xend.XendDomainInfo")
#log.setLevel(logging.TRACE)
@@ -972,6 +974,28 @@ class XendDomainInfo:
"""Set the memory target of this domain.
@param target In MiB.
"""
+
+ if self.domid == PRIV_DOMAIN:
+ dom0_min_mem = xroot.get_dom0_min_mem()
+
+ if dom0_min_mem == 0:
+ raise VmError('Cannot balloon privileged domain memory '
+ 'since dom0_min_mem is set to 0.')
+ elif target < dom0_min_mem:
+ raise VmError(('Cannot shrink privileged domain memory '
+ 'to less than dom0_min_mem (%d MiB).') %
+ (dom0_min_mem))
+ else:
+ domU_min_mem = xroot.get_domU_min_mem()
+
+ if domU_min_mem == 0:
+ raise VmError('Cannot balloon domain memory '
+ 'since domU_min_mem is set to 0.')
+ elif target < domU_min_mem:
+ raise VmError(('Cannot shrink domain memory '
+ 'to less than domU_min_mem (%d MiB).') %
+ (domU_min_mem))
+
log.debug("Setting memory target of domain %s (%d) to %d MiB.",
self.info['name'], self.domid, target)
diff -r 062d109ce872 tools/python/xen/xend/XendRoot.py
--- a/tools/python/xen/xend/XendRoot.py Thu May 11 22:39:44 2006 +0100
+++ b/tools/python/xen/xend/XendRoot.py Fri May 12 11:29:53 2006 -0400
@@ -95,6 +95,8 @@ class XendRoot:
dom0_min_mem_default = '0'
dom0_vcpus_default = '0'
+
+ domU_min_mem_default = '64'
components = {}
@@ -269,6 +271,9 @@ class XendRoot:
def get_dom0_vcpus(self):
return self.get_config_int('dom0-cpus', self.dom0_vcpus_default)
+ def get_domU_min_mem(self):
+ return self.get_config_int('domU-min-mem', self.domU_min_mem_default)
+
def get_console_limit(self):
return self.get_config_int('console-limit', 1024)
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply
* Re: git-bisect failed me again
From: Linus Torvalds @ 2006-05-12 16:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: junkio, git
In-Reply-To: <Pine.LNX.4.64.0605120823170.3866@g5.osdl.org>
On Fri, 12 May 2006, Linus Torvalds wrote:
>
> But git isn't linear. Never has been. The fact that commits get (roughtly)
> sorted by date (modified by their ancestry relationships either subtly or
> grossly depending on whether --topo-sort is off or on) does not make
> anything linear.
Note that totally independently of sort order (whether "topo-order" or the
normal cheaper "order by date, but at least one chain of parenthood always
first"), you _will_ get the situation that a commit that was shown "last"
in a linear list is actually merged long before.
The simplest case is this:
merge
| \
A \
| \
B \
| X
C |
| Y
D |
| Z
.. ..
where the "main branch" is the A-B-C-D.. line of history, and the merge
brings in another "X-Y-Z" line of history.
Now, the A-B-C branch may have gotten a lot more recent love and
attention, and when you linearize it, since the normal ordering tends to
show it in a date-like order, you may get a list of commits like
merge
A
B
C
D
..
X
Y
Z
..
which makes you think that "A" is much more recent than "X". That may be
actually be _true_, but:
- 'X' actually _showed_up_ in the mainline much later than A. So, if you
track another persons tree like this, X as a commit may be 2 weeks old,
but it might not have been in the tree you tracked yesterday, because
it hadn't been _merged_ until today.
So in a very real sense, from your standpoint, 'X' may be the 'recent'
one, because you hadn't seen it before, but you _had_ seen 'A'
yesterday.
- Equally importantly, 'A' very much is _not_ a descendant of 'X' (ie,
'X' is _not_ reachable from 'A'). So even though 'A' is in a time-sense
much more recent than 'X', you can't say "it's the most recent commit,
so if there's a bug in any of the series, the bug must have been
visible at point 'A'".
This is why it's wrong to look at _any_ linearized list of commits and
imply any ordering what-so-ever. There simply is no list ordering that
guarantees anything at all, because even with "topo-sort", the only thing
we guarantee is that commits that are directly related to each other will
always sort the child before its parents. So even there, you can't
actually say that one commit "dominates" another commit unless you end up
looking at the parenthood chain (and merges are really important).
[ Strictly speaking, there is exactly _one_ thing you can say from just
seeing a list of commits: _if_ that list includes all types of commits
(ie notably merges and empty changes) _and_ if that list was generated
with just one "top" commit, then the first commit on the list will
dominate all other commits. But that's literally the only real ordering
you can ever know from just a list.
So looking at the first commit in a list is actually valid, but only if
you included all the merges and only if the list was generated by a git
command, and not sorted by any other criteria ]
Linus
^ permalink raw reply
* Re: 3c59x vortex_timer rt hack (was: rt20 patch question)
From: Steven Rostedt @ 2006-05-12 16:11 UTC (permalink / raw)
To: Andrew Morton; +Cc: mingo, markh, linux-kernel, dwalker, tglx
In-Reply-To: <20060512090323.252d8600.akpm@osdl.org>
On Fri, 12 May 2006, Andrew Morton wrote:
> >
> > The vortex_timer is a timeout,
>
> err, it's actually a function.
OK, I meant vp->timer
>
> > will it go off often?
>
> Every five seconds if the cable's unplugged. Every 60 seconds otherwise.
>
OK, so the function is a service and not a fixup (or both). Hmm, so
latency is an issue.
Thanks,
-- Steve
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.