On Friday 11 March 2005 03:03, Christoph Lameter wrote:
> Changelog:
> - use Kconfig and CONFIG_CLEAR_PAGES
>
> The zeroing of a page of a arbitrary order in page_alloc.c and in hugetlb.c
> may benefit from a
> clear_page that is capable of zeroing multiple pages at once. The following
> patch a
> "Greg" == Greg KH <[EMAIL PROTECTED]> writes:
Greg> On Fri, Mar 11, 2005 at 02:37:17PM +1100, Peter Chubb wrote:
>> +/* + * The PCI subsystem is implemented as yet-another pseudo
>> filesystem, + * albeit one that is never mounted. + * This is its
>> magic number. + */ +#define USR_PCI_MAG
> "Andi" == Andi Kleen <[EMAIL PROTECTED]> writes:
Andi> Andrew Morton <[EMAIL PROTECTED]> writes:
>> Why does the kernel need this feature?
>>
>> Have you any numbers on the overhead?
Andi> It does RDTSC and lots of complicated stuff twice for each
Andi> system call. On P4 this will be ext
Andrew Morton writes:
> This patch causes the non-numa G5 to oops very early in boot in
> smp_call_function().
Hmmm, the reason we are getting into smp_call_function is that we have
panicked due to not being able to allocate boot memory. It's kind of
sad that we can't even panic successfully, al
Hi Christian,
I would like to know what are the kernel versions this problem happened.
Did this problem start from 2.6.11-rc2-bk10?
BR,
Mauricio Lin.
On Thu, 10 Mar 2005 16:12:27 +0100, Christian Kujau <[EMAIL PROTECTED]> wrote:
> ok,
>
> as "promised", it the OOM happened again with the same
Hi all,
I'm not sure if someone else did this, but I wrote this simple script that
turns off the modules from your config file that you are not currently
using. After downloading a new kernel I usually use the .config from my
Debian distribution. But this usually has way too many modules turned
Andrew Morton wrote:
:
: in_atomic() is not a reliable indication of whether it is currently safe
: to call schedule().
:
: This is because the lockdepth beancounting which in_atomic() uses is only
: accumulated if CONFIG_PREEMPT=y. in_atomic() will return false inside
: spinlocks if CONFIG_PREE
Hi Greg, all,
> > Not that I really care, but isn't there a rule that a patch "... can
> > not contain any "trivial" fixes in it (spelling changes, whitespace
> > cleanups, etc.)"?
>
> Good point. Jean, care to respin the patch?
Sure, sorry for the trouble.
---
This is a rewrite of the saa711
Hello all,
I've just found following messages in dmesg of my smp
amd64 box. Is this a sign of broken hardware (box passed
memtest86 for 24 hours two months ago) or kernel problem?
mm/memory.c:97: bad pmd 81009773fc78(2aaabab8).
mm/memory.c:97: bad pmd 81009773fc80(0003
i have released the -V0.7.40-00 Real-Time Preemption patch, which can be
downloaded from the usual place:
http://redhat.com/~mingo/realtime-preempt/
this is a merge to 2.6.11-final.
to create a -V0.7.40-00 tree from scratch, the patching order is:
http://kernel.org/pub/linux/kernel/v2.6/li
* Chen, Kenneth W <[EMAIL PROTECTED]> wrote:
> # size vmlinux.*
>textdata bss dec hex filename
> 3261844 717184 262020 4241048 40b698 vmlinux.x86.orig
> 3262772 717488 262020 4242280 40bb68 vmlinux.x86.inline
> Possible we can introduce them back?
> -static unsigned in
* Scott Wood <[EMAIL PROTECTED]> wrote:
> - p->prio = effective_prio(p);
> + /* Don't overwrite an inherited RT priority with the static
> +RT priority. */
> +
> + if (!rt_task(p))
> + p->prio = effective_prio(p);
are you sure this is needed? The -RT code currentl
On Thu, 2005-03-10 at 23:17 -0800, Andrew Morton wrote:
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
> >
> > The iMac G5 and new single CPU PowerMac G5 come with a new revision of
> > the K2 ASIC called Shasta. The PATA cell in there now does 133Mhz. This
> > patch adds support for it. It
Le jeudi 10 mars 2005 à 11:28 -0500, John Richard Moser a écrit :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I've been looking at the UDI project[1] and thinking about binary
> drivers and the like, and wondering what most peoples' take on these are
> and what impact that UDI support wo
* Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> > Ingo, we already have a touch_nmi_watchdog() in the sysrq code. It might be
> > worth adding a touch_softlockup_watchdog() wherever we have a
> > touch_nmi_watchdog().
>
> or add touch_softlockup_watchdog to touch_nmi_watchdog() instead
> an
Hi!
Where do I get latest version of `subj`? I guess I should do some
hacking...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsu
Jan Kasprzak <[EMAIL PROTECTED]> wrote:
>
> This may be the cause of
>
> http://bugme.osdl.org/show_bug.cgi?id=4150
Looks that way, yes.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.ke
On Thu, 10 Mar 2005 20:59:43 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote:
> jerome lacoste <[EMAIL PROTECTED]> wrote:
> >
> > On an VIA EPIA board, I got this single oops at boot. Wasn't stored on
> > file so I had to take a screenshot with a digital camera. Basicallly
> > goes along those lines
* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> > The short term fix is probably to put back the preempt_disables, the long
> > term is to get rid of these stupid bit_spin_lock busy loops.
>
> Doing a quick search on the kernel, it looks like only kjournald uses
> the bit_spin_locks. I'll start co
Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
>
> * Arjan van de Ven <[EMAIL PROTECTED]> wrote:
>
> > > Ingo, we already have a touch_nmi_watchdog() in the sysrq code. It might
> > > be
> > > worth adding a touch_softlockup_watchdog() wherever we have a
> > > touch_nmi_watchdog().
> >
> > or ad
On Fri, 11 Mar 2005, Ingo Molnar wrote:
>
> * Steven Rostedt <[EMAIL PROTECTED]> wrote:
>
> > > The short term fix is probably to put back the preempt_disables, the long
> > > term is to get rid of these stupid bit_spin_lock busy loops.
> >
> > Doing a quick search on the kernel, it looks like on
* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> > > Doing a quick search on the kernel, it looks like only kjournald uses
> > > the bit_spin_locks. I'll start converting them to spinlocks. The use
> > > seems to be more of a hack, since it is using bits in the state field
> > > for locking, and the
Hello Linus,
you can either use "bk receive" to patch with this mail,
or you can
Pull from: bk://krusty.dt.e-technik.uni-dortmund.de/BK-kernel-tools
or in cases of dire need, you can apply the patch below.
BK parent: http://bktools.bkbits.net/bktools
Patch description:
[EMAIL PROTECTED], 2005-03
On Ät 10-03-05 13:25:19, Lee Revell wrote:
> On Thu, 2005-03-10 at 09:31 -0800, Greg KH wrote:
> > On Thu, Mar 10, 2005 at 12:27:23PM -0500, Lee Revell wrote:
> > > On Thu, 2005-03-10 at 08:43 -0800, Greg KH wrote:
> > > > That, and a zillion other specific wordings that people suggested fall
> > >
On Fri, 11 Mar 2005, Ingo Molnar wrote:
>
> * Steven Rostedt <[EMAIL PROTECTED]> wrote:
> > I've tried making two global spinlocks, one for the state bit and one
> > for the journal head bit use. But this deadlocks with j_state_lock.
> > The journal head lock seems to be ok to be global, but the
* Andrew Morton <[EMAIL PROTECTED]> wrote:
> We should arrange for touch_softlockup_watchdog() to be called
> whenever touch_nmi_watchdog() is called.
the patch below adds a touch_softlockup_watchdog() call to every
touch_nmi_watchdog() call.
[A future consolidation patch should introduce a tou
Hi!
> As many of you will be aware, we've been working on infrastructure for
> user-mode PCI and other drivers. The first step is to be able to
> handle interrupts from user space. Subsequent patches add
> infrastructure for setting up DMA for PCI devices.
>
> The user-level interrupt code doesn
Hi!
> >> +/* + * The PCI subsystem is implemented as yet-another pseudo
> >> filesystem, + * albeit one that is never mounted. + * This is its
> >> magic number. + */ +#define USR_PCI_MAGIC (0x12345678)
>
> Greg> If you make it a real, mountable filesystem, then you don't need
> Greg> to have a
On Thu, Mar 10, 2005 at 05:45:22PM -0500, Rik van Riel wrote:
> On Thu, 10 Mar 2005, John Richard Moser wrote:
>
> > A Linux specific binary driver format might be more useful,
>
> No, it wouldn't. I can use a source code driver on x86,
> x86-64 and PPC64 systems, but a binary driver is only
> u
Steven Rostedt <[EMAIL PROTECTED]> wrote:
>
> > did you try the canonical way of putting a spinlock into every
> > buffer_head?
> >
>
> No, I'll try that now. I just didn't want to modify the buffer head struct
> just for journaling. But if it is the quickest and easiest fix, then I'll
> sub
On Fri, 11 Mar 2005, Andrew Morton wrote:
> Steven Rostedt <[EMAIL PROTECTED]> wrote:
> > No, I'll try that now. I just didn't want to modify the buffer head struct
> > just for journaling. But if it is the quickest and easiest fix, then I'll
> > submit it and we can change it later.
>
> You
In file mm/oom_kill.c, uncomment line 24: /* #define DEBUG */.
And next time when oom happens again, we'll see the badness.
--coywolf
On Tue, 08 Mar 2005 16:21:21 +0100, Christian Kujau <[EMAIL PROTECTED]> wrote:
> hallo list,
>
> today my machine went out out memory and noticing it several hou
On Gwe, 2005-03-11 at 01:42, Andrew Morton wrote:
> So.. did we end up deciding that the Geode patch should be reverted
> wholesale?
Either revert it or make it Geode GX and correct the options set. I've
no problem with a Geode option that sets the right options 8)
-
To unsubscribe from this lis
Hello,
I'm testing a pair of new servers we just bought.
They are HP DL585 dual Opteron 844 with 8G RAM, RAID1 over 2x72G SCSI disks
(HP CISS driver) and running 2.6.11. In /proc/driver/cciss/cciss0 we have:
cciss0: HP Smart Array 5i Controller
Board ID: 0x40800e11
Firmware Version: 2.56
IRQ:
Hi,
One line summary of the problem:CompactFlash mount results in Oops
Full description of the problem/report:
When mounting a CF card, the error occurs resulting in pretty unusable system.
Keywords (i.e., modules, networking, kernel):
ide_cs.ko
compact flash card
mount
Oops
/proc/vers
On Friday 11 March 2005 13:08, Simone Piunno wrote:
>
> Hello,
>
> I'm testing a pair of new servers we just bought.
> They are HP DL585 dual Opteron 844 with 8G RAM, RAID1 over 2x72G SCSI disks
> (HP CISS driver) and running 2.6.11. In /proc/driver/cciss/cciss0 we have:
>
> cciss0: HP Smart A
Hello All,
I have a question regarding the wait queues. I have a driver
pxausb_core.o which is the core driver which does all USB endpoint
handling and hardware interaction. I have one more driver on top of it
usb-serial which provides for the user-level interaction(like read,
write, ioctl).
I have
Russell King <[EMAIL PROTECTED]> wrote:
> With current-ish Linus 2.6 BK, I'm seeing this:
>
> net/ipv4/netfilter/ipt_hashlimit.c:96: warning: type defaults to `int' in
> declaration of `DECLARE_LOCK'
> net/ipv4/netfilter/ipt_hashlimit.c:96: warning: parameter names (without
> types) in function
Hi all,
I tried to disable fastpath code in tcp_rcv_established() (i suppose i need
this for some debugging purposes)
by commenting out corresponding lines 4110-4252 in net/ipv4/tcp_input.c (kernel
ver 2.4.28)
after recompiling kernel doesn't want to transmit tcp packets properly and even
segmen
On Friday 11 March 2005 09:28, Ingo Molnar wrote:
> i have released the -V0.7.40-00 Real-Time Preemption patch, which can be
> downloaded from the usual place:
>
I've lost the thread a little; Is this still x86 only?
Andrew Walrond
-
To unsubscribe from this list: send the line "unsubscribe linux
I just had some issues with ssh and trying to get it to bind to all ipv6
and ipv4 addresses to it via :: and 0.0.0.0. The problem was that it'd
only let one succeed. If 0.0.0.0:22 was successful then :: port 22 could
not happen and neither could my ipv6 addy port 22 as it would get the
'address alr
On Thu, Mar 10, 2005 at 09:56:52PM -0800, Andrew Morton wrote:
> That's a nice application of semaphores. I can see that there's also a
> need to be able to read the value back for reporting purposes. Dang.
>
> But I guess it's a bit hard to justify adding more infrastructure to
> support a sing
This patch extracts all the operations on counters protected by the
page table lock (currently rss and anon_rss) into definitions in
include/linux/sched.h. All rss operations are performed through
the following three macros:
get_mm_counter(mm, member) -> Obtain the value of a counter
>
> I don't understand. Does the kernel code need to wait for the helper
> to finish while holding the semaphore? AFAICS, the helper is completely
> asynchronous, so it can simply do its job when the kernel has given
> up the semaphore.
It should be totally async witout any sem. there is no guar
On Fri, 2005-03-11 at 01:46 -0800, Andrew Morton wrote:
> Jan Kasprzak <[EMAIL PROTECTED]> wrote:
> >
> > This may be the cause of
> >
> > http://bugme.osdl.org/show_bug.cgi?id=4150
>
> Looks that way, yes.
Note that it would be interesting to fix that (I mean the reliability of
is_atomic() or
On Thu, 10 Mar 2005 17:08:55 +0100, Arjan van de Ven
<[EMAIL PROTECTED]> wrote:
> On Thu, 2005-03-10 at 17:00 +0100, Lorenzo Hernández García-Hierro
> wrote: it tries to fill the
> > ipaddr member of the task_struct structure with the IP address
> > associated to the user running @current task/proc
On Thu, 2005-03-10 at 20:53 -0800, Roland Dreier wrote:
> > Consequently the use of in_atomic() in the below files is probably
> > deadlocky if CONFIG_PREEMPT=n:
> ...
> > drivers/infiniband/core/mad.c
>
> Thanks for pointing this out. I'll get you a patch in the next day
On Thu, 10 Mar 2005, Matthew Wilcox wrote:
+extern unsigned int pirq_table_addr;
Completely nitpicking, but I think this should be an unsigned long rather
than an int -- physical addresses are normally expressed in terms of
unsigned long.
Yup, good point, I'll fix that.
Should we fall back to searc
This patch allows to aggregate multiple page faults into a single one. It
does that by detecting that an application generates a sequence of page
faults.
If a fault occurred for page x and is then followed by page x+1 then it may
be reasonable to expect another page fault at x+2 in the future. If
In article <[EMAIL PROTECTED]> you wrote:
> With version 2.6.10 the driver for the tuner frontend from ALPS TDLB7
> was removed.
>
> Why do you think that this is a dead file?
> While I'm happy with the work you do for dvb on Linux, and I want to
> thank you for this anyway, my TV does not work
Hi!
> This patch has been spitting warnings:
>
> drivers/usb/host/uhci-hcd.c:838: warning: initialization from incompatible
> pointer type
> drivers/usb/host/ohci-pci.c:191: warning: initialization from incompatible
> pointer type
>
> Because hc_driver.suspend() takes a u32 as its second arg.
Hi!
> This patch has been spitting warnings:
>
> drivers/usb/host/uhci-hcd.c:838: warning: initialization from incompatible
> pointer type
> drivers/usb/host/ohci-pci.c:191: warning: initialization from incompatible
> pointer type
>
> Because hc_driver.suspend() takes a u32 as its second arg.
Hi,
On an embedded device based on the IBM 405GP, but this may be a general
problem for most PPC platforms except for chrp and gemini, the NTP
utility 'ntptime' always returns error code 5 (TIME_ERROR) even after
that NTP status reaches the PLL and FLL state. Analysis of problem
showed that the
Alle 12:35, venerdì 11 marzo 2005, Denis Vlasenko ha scritto:
> >
> > Unresponsiveness is not 2.6.11 specific (we've seen the same thing on
> > 2.6.10 and 2.6.8), not I/O scheduler specific ("as" and "deadline" behave
> > the same) and not CPU/SMP specific (reproduced on single P4 HT and single
>
Fabio Coatti wrote:
Alle 12:35, venerdì 11 marzo 2005, Denis Vlasenko ha scritto:
Unresponsiveness is not 2.6.11 specific (we've seen the same thing on
2.6.10 and 2.6.8), not I/O scheduler specific ("as" and "deadline" behave
the same) and not CPU/SMP specific (reproduced on single P4 HT and single
Fix cyrix section references:
convert __initdata to __devinitdata.
Error: ./arch/i386/kernel/cpu/mtrr/cyrix.o .text refers to 0379
R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/mtrr/cyrix.o .text refers to 0399
R_386_32 .init.data
Error: ./arch/i386/kernel/cpu/mtrr/c
I have many users asking for something like this. Peter's approach is
simple and it appears to solve the problem for many situations.
With that in mind though, for a more complicated but higher performing
approach please take a look at the User Level Interrupt (ULI) project at
http://oss.s
Dmitry Torokhov wrote:
My box gets stuck while booting (actually starting ntpd) whith tonight
pull from Linus. It looks like it is spinning in ipt_do_table when I do
SysRq-P. No call trace though.
Please post your ruleset and .config. A backtrace would also be
useful.
Anyone else seeing it? Any ide
On Fri, 11 Mar 2005 09:44:28 +1100
Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
>
> > /* Free memory returned from module_alloc */
> > diff -puN arch/ppc64/mm/fault.c~nx-kernel-ppc64 arch/ppc64/mm/fault.c
> > --- linux-2.6-bk/arch/ppc64/mm/fault.c~nx-kernel-ppc64 2005-03-10
> > 13:
On Fri, Mar 11, 2005 at 11:02:33AM +, Alan Cox wrote:
> Either revert it or make it Geode GX and correct the options set. I've
> no problem with a Geode option that sets the right options 8)
Maybe it should say GX1 unless someone is sure the GX1 and GX2 (now GX
[EMAIL PROTECTED] it seems) like
Hi!
This fixes suspend-resume on via-velocity. It was confused
w.r.t. pointers... Please apply,
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
Pavel
--- clean-mm/drivers/net/via-velocity.c 2005-03-11 11:25:36.0 +0100
+++ linux/driv
From: Stefan <[EMAIL PROTECTED]>
In platform swsusp mode, we were forgetting to spin disks down,
leading to ugly emergency shutdown. This synchronizes platform method
with other methods and actually helps. Please apply,
Pavel
Signed
>> >
>> > Unresponsiveness is not 2.6.11 specific (we've seen the same thing on
>> > 2.6.10 and 2.6.8), not I/O scheduler specific ("as" and "deadline" behave
>> > the same) and not CPU/SMP specific (reproduced on single P4 HT and single
>> > P3), but only on these two DL585 servers we've seen bonn
CaT wrote:
I just had some issues with ssh and trying to get it to bind to all ipv6
and ipv4 addresses to it via :: and 0.0.0.0. The problem was that it'd
only let one succeed. If 0.0.0.0:22 was successful then :: port 22 could
not happen and neither could my ipv6 addy port 22 as it would get the
'
Kernel 2.6 (2.6.11)
When ethernet-bridge forward a packet and such ethernet-frame has
VLAN-tag, bridge should update skb->prioriry for properly QoS
handling. This small patch does this.
Based upon discussion during last week I added pskb_may_pull()
checking and simple mapping from 802.1p/user_pri
Hello,
just a reminder for the next time - please keep the lines length under 80
characters.
> Detailed Description
> -
> I am using Core Linux system on flashcard. Its another minimal linux
> distribution. Root filesystem is cramfs and a rw partition on flash is
>
Here's the patch. It's probably more of an overkill wrt buffer heads, but
it seems to be the easiest solution.
I also put back some of the changes you made for the
bit_spin_locks, so that they act the same as the vanilla kernel if
PREEMPT_RT is not defined. Now I only tested this with PREEMPT_R
Benjamin Herrenschmidt wrote:
On Thu, 2005-03-10 at 11:05 -0600, Omkhar Arasaratnam wrote:
2.6.10 seems to have a different kernel panic which I'm investigating
(could be a problem with my ramdisk as it happens in my linuxrc). So
long story short the 2.6.10 sym driver looks ok.
Can you tr
Hi,
Another patch for 2.6.11.x: already in main tree, fixes kernel panic
on receive with WAN cards based on Hitachi SCA/SCA-II: N2, C101,
PCI200SYN.
Also a documentation change fixing user-panic can-t-find-required-software
failure (just the same patch as in mainline) :-)
Please apply, thanks.
--
In article <[EMAIL PROTECTED]> (at Fri, 11 Mar 2005 23:16:55 +1100), CaT
<[EMAIL PROTECTED]> says:
> If it bound to :: port 22 then 0.0.0.0:22 would fail.
>
> On the other hand if I got it to bind to each address individually then
> both ipv4 (2 addresses) and ipv6 (1 address) binds would succee
Hello,
The attached patch is an attempt to work around the buggy timestamp
counter on the NatSemi SC1100 CPU by using the on-board 27MHz
high-resolution timer as an alternative time source. It should,
in theory, work with any of the SCx200 CPUs as well, though I have
been unable to test this. I
Mauricio Lin wrote:
> Hi Christian,
>
> I would like to know what are the kernel versions this problem happened.
>
> Did this problem start from 2.6.11-rc2-bk10?
i noticed it first at 2.6.11, then again with 2.6.11-rc5-bk2. suspecting
pppd to be the culprit to chew up all RAM after being termina
>
> +#ifdef CONFIG_PREEMPT_RT
> +#define PICK_SPIN_LOCK(otype,bit,name) spin_##otype(&bh->b_##name##_lock)
> +#else
> +#define PICK_SPIN_LOCK(otype,bit,name) bit_spin_##otype(bit,bh->b_state);
> +#endif
> +
Oops, extra semicolon on the non RT side.
I'll try again.
-- Steve
diff -ur linux-2.6.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Coywolf Qi Hunt wrote:
> In file mm/oom_kill.c, uncomment line 24: /* #define DEBUG */.
> And next time when oom happens again, we'll see the badness.
oh, good hint. will do this before the next reboot (in a few hours i guess)
thanks,
Christian.
-
On Fri, Mar 11 2005, Simone Piunno wrote:
> Alle 14:29, venerdì 11 marzo 2005, Baruch Even ha scritto:
>
> > echo t > /proc/sysrq-trigger
>
> Before killing bonnie:
I'm guessing your problem is that bonnie dirtied tons of data before you
killed it, so it has to flush it out. If you run out of re
On Fri, Mar 11, 2005 at 08:58:15AM -0600, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> > If it bound to :: port 22 then 0.0.0.0:22 would fail.
> >
> > On the other hand if I got it to bind to each address individually then
> > both ipv4 (2 addresses) and ipv6 (1 address) binds would succeed.
> >
> >
On Fri, Mar 04 2005, Vincent Vanackere wrote:
> > Added since 2.6.10-ck7:
> > +cfq-ts-21.diff
> > The latest version of Jens' cfq-timeslice i/o scheduler now heavily tested
> > and
> > with full read i/o priority support
>
> Speaking of the cfq-timeslice scheduler, is there a version that
> appli
On Fri, Mar 11, 2005 at 07:34:46PM +1100, Peter Chubb wrote:
> > "Greg" == Greg KH <[EMAIL PROTECTED]> writes:
>
> Greg> On Fri, Mar 11, 2005 at 02:37:17PM +1100, Peter Chubb wrote:
> >> +/* + * The PCI subsystem is implemented as yet-another pseudo
> >> filesystem, + * albeit one that is neve
OHGAWD I GOT IT
I admit, totally coincidentially but its really FIXED. Today I went to the puter scanning the
servers by routine and wondered why the bandwidth is at 100% without any holes.
The only thing I have done is I switched off hyper-threading because the server is at only 20% CPU
Greg KH wrote:
On Wed, Mar 09, 2005 at 12:18:21PM -0500, Wen Xiong wrote:
Greg KH wrote:
On Wed, Mar 09, 2005 at 10:47:22AM -0500, Wen Xiong wrote:
+static ssize_t jsm_driver_debug_show(struct device_driver *ddp, char
*buf)
+{
+ return snprintf(buf, PAGE_SIZE, "0x%x\n", jsm_debug);
Steven Rostedt wrote:
+#ifdef CONFIG_PREEMPT_RT
+#define PICK_SPIN_LOCK(otype,bit,name) spin_##otype(&bh->b_##name##_lock)
+#else
+#define PICK_SPIN_LOCK(otype,bit,name) bit_spin_##otype(bit,bh->b_state);
+#endif
+
Oops, extra semicolon on the non RT side.
I'll try again.
-- Steve
Haven't tried it
The second patch for new jsm serial device driver.
Signed-off-by: Wen Xiong <[EMAIL PROTECTED]>
diff -Nuar linux-2.6.11.org/drivers/serial/jsm/jsm_tty.c
linux-2.6.11.new/drivers/serial/jsm/jsm_tty.c
--- linux-2.6.11.org/drivers/serial/jsm/jsm_tty.c 1969-12-31
18:00:00.0 -0600
+++ li
The fouth patch for jsm serial device driver.
Signed-off-by: Wen Xiong <[EMAIL PROTECTED]>
diff -Nuar linux-2.6.11.org/drivers/serial/jsm/jsm.h
linux-2.6.11.new/drivers/serial/jsm/jsm.h
--- linux-2.6.11.org/drivers/serial/jsm/jsm.h 1969-12-31 18:00:00.0
-0600
+++ linux-2.6.11.new/driver
The third patch for jsm device driver.
Signed-off-by: Wen Xiong <[EMAIL PROTECTED]>
diff -Nuar linux-2.6.11.org/drivers/serial/jsm/jsm_neo.c
linux-2.6.11.new/drivers/serial/jsm/jsm_neo.c
--- linux-2.6.11.org/drivers/serial/jsm/jsm_neo.c 1969-12-31
18:00:00.0 -0600
+++ linux-2.6.11.n
* Steven Rostedt <[EMAIL PROTECTED]> wrote:
> Here's the patch. It's probably more of an overkill wrt buffer heads,
> but it seems to be the easiest solution.
isnt there some ext3-private journal structure (journal-bh) linked off
the bh? If the lock is in that structure then the overhead would
This is fifth patch for jsm serial device driver.
Signed-off-by: Wen Xiong <[EMAIL PROTECTED]>
diff -Nuar linux-2.6.11.org/drivers/serial/Kconfig
linux-2.6.11.new/drivers/serial/Kconfig
--- linux-2.6.11.org/drivers/serial/Kconfig 2005-03-10 16:28:59.552930408
-0600
+++ linux-2.6.11.new/driver
On Mon, 2005-03-07 at 16:55 +0100, Raphael Jacquot wrote:
[...]
> as your name appears european, there are no software patents (yet ?) so
Alas, this is wrong. The EPO is issuing masses of software patents since
years (though they are more or less explicitly[0] excluded from
patentability in the E
Alle 16:16, venerdì 11 marzo 2005, Jens Axboe ha scritto:
> On Fri, Mar 11 2005, Simone Piunno wrote:
> > Alle 14:29, venerdì 11 marzo 2005, Baruch Even ha scritto:
> > > echo t > /proc/sysrq-trigger
> >
> > Before killing bonnie:
>
> I'm guessing your problem is that bonnie dirtied tons of data be
On Fri, Mar 11 2005, Fabio Coatti wrote:
> Alle 16:16, venerdì 11 marzo 2005, Jens Axboe ha scritto:
> > On Fri, Mar 11 2005, Simone Piunno wrote:
> > > Alle 14:29, venerdì 11 marzo 2005, Baruch Even ha scritto:
> > > > echo t > /proc/sysrq-trigger
> > >
> > > Before killing bonnie:
> >
> > I'm gue
On Fri, 2005-03-11 at 10:38 -0500, Wen Xiong wrote:
> +static void neo_set_cts_flow_control(struct jsm_channel *ch)
> +{
> + u8 ier = readb(&ch->ch_neo_uart->ier);
> + u8 efr = readb(&ch->ch_neo_uart->efr);
> +
...
> +
> + writeb(ier, &ch->ch_neo_uart->ier);
> +}
Hi,
have you ever a
Alle 16:54, venerdì 11 marzo 2005, Jens Axboe ha scritto:
> I'd guess that your problem is queueing, if you have a ton of pending
> requests in the hardware it will take forever to get a new request
> through. There's nothing the io scheduler can do to help you there,
> really. The /proc/driver/cc
On Fri, Mar 11 2005, Simone Piunno wrote:
> Alle 16:54, venerdì 11 marzo 2005, Jens Axboe ha scritto:
>
> > I'd guess that your problem is queueing, if you have a ton of pending
> > requests in the hardware it will take forever to get a new request
> > through. There's nothing the io scheduler can
On Fri, 11 Mar 2005, Ingo Molnar wrote:
>
> * Steven Rostedt <[EMAIL PROTECTED]> wrote:
>
> > Here's the patch. It's probably more of an overkill wrt buffer heads,
> > but it seems to be the easiest solution.
>
> isnt there some ext3-private journal structure (journal-bh) linked off
> the bh? If
On Thu, 10 Mar 2005 12:24:15 -0500, John Richard Moser
<[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I've done more thought, here's a small list of advantages on using
> binary drivers, specifically considering UDI. You can consider a
> different implementation
On Fri, Mar 11, 2005 at 10:36:07AM +0100, Ingo Molnar wrote:
>
> * Scott Wood <[EMAIL PROTECTED]> wrote:
>
> > - p->prio = effective_prio(p);
> > + /* Don't overwrite an inherited RT priority with the static
> > + RT priority. */
> > +
> > + if (!rt_task(p))
> > + p->prio = e
Alle 17:00, venerdì 11 marzo 2005, Jens Axboe ha scritto:
> > It was after running bonnie++.
>
> Are you sure? It lists only 190 commands run since it initialized,
> that's basically nothing.
Yes I'm sure!
Isn't this number the MAX value ever samplef for "Current # commands on
controller"? It
[EMAIL PROTECTED] said:
> Can't we just fix it by havign an alias for both names? It seems
> stupid to jump through hoops and worry about compiler versions, when
> afaik we could just do something like
> extern (...) __attribute__((alias("")));
> instead. Exact details left to the
[EMAIL PROTECTED] said:
> This patch is still wrong.
> It seems my comment on this [1] was lost:
> <-- snip -->
> This line has to be something like
> ( (__GNUC__ == 3 && __GNUC_MINOR__ == 3 && __GNUC_PATCHLEVEL__ >= 4)
> && \
>HEAVILY_PATCHED_SUSE_GCC )
> I hope SuSE has added some #define
* Jean Delvare ([EMAIL PROTECTED]) wrote:
> Hi Greg, all,
>
> > > Not that I really care, but isn't there a rule that a patch "... can
> > > not contain any "trivial" fixes in it (spelling changes, whitespace
> > > cleanups, etc.)"?
> >
> > Good point. Jean, care to respin the patch?
>
> Sure,
On Thursday, March 10, 2005 8:30 pm, Benjamin Herrenschmidt wrote:
> On Thu, 2005-03-10 at 20:02 -0800, Jesse Barnes wrote:
> > On Thursday, March 10, 2005 6:38 pm, Benjamin Herrenschmidt wrote:
> > > That one is even worse... from what I see in your lspci output, you
> > > have no bridge with AGP
1 - 100 of 304 matches
Mail list logo