Lee Revell wrote: {
On Fri, 2005-07-22 at 21:15 -0500, Alejandro Bonilla wrote:
> OK, I will, but I first of all need to learn how to tell if benchmarks
> are better or worse.
Con's interactivity benchmark looks quite promising for finding scheduler
related interactivity regressions.
}
Adrian Bunk wrote: {
On Fri, Jul 22, 2005 at 07:55:48PM +0100, christos gentsis wrote:
> i would like to ask if it possible to change the optimization of the
> kernel from -O2 to -O3 :D, how can i do that? if i change it to the
> top level Makefile does it change to all the Makefiles?
And since
Dick Johnson wrote: {
> On Fri, 2005-07-22 at 08:27 -0300, Vinicius wrote:
> [...]
>>I have a server with 2 Pentium 4 HT processors and 32 GB of RAM,
>> this server runs lots of applications that consume lots of memory to.
>> When I stop this applications, the kernel doesn't free memory
Russell King <[EMAIL PROTECTED]> wrote:
>
> Guys,
>
> ARM folk have recently pointed out a problem with sys_times().
> When the kernel boots, we set jiffies to -5 minutes. This causes
> sys_times() to return a negative number, which increments through
> zero.
>
> However, some negative numbers
Hi Linus,
Please pull from:
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/lenb/linux-2.6.git/
for a single patch that removes some recently added
debugging console messages.
thanks!
-Len
ec.c | 17 +++--
1 files changed, 3 insertions(+), 14 deletions(-)
commit
-
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.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Michael Harris wrote:
>
> [2.] The problem occurs in a forking server similar in function to
> inetd. The server employs a very simple SIGCHLD handler that loops on
> wait(2), until all zombie processes have been collected. For no
> immediately apparent reason, the parent process behaves as if
On Fri, 2005-07-22 at 20:23 -0400, Mark Hahn wrote:
> > > actually, let me also say that CKRM is on a continuum that includes
> > > current (global) /proc tuning for various subsystems, ulimits, and
> > > at the other end, Xen/VMM's. it's conceivable that CKRM could wind up
> > > being useful
On Fri, Jul 22, 2005 at 09:15:14PM -0500, Alejandro Bonilla wrote:
> Lee Revell wrote:
>
> >On Fri, 2005-07-22 at 20:07 -0500, Alejandro Bonilla wrote:
> >
> >>I will get flames for this, but my laptop boots faster and sometimes
> >>responds faster in 2.4.27 than in 2.6.12. Sorry, but this is
On Friday 22 July 2005 19:28, Pavel Machek wrote:
> This adds support for touchscreen on Sharp Zaurus sl-5500. Vojtech,
> please apply,
I have couple more commnets...
> +static int ucb1x00_thread(void *_ts)
> +{
> + struct ucb1x00_ts *ts = _ts;
> + struct task_struct *tsk = current;
> +
On Fri, Jul 22, 2005 at 11:05:59PM -0400, YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <[EMAIL PROTECTED]> (at Sat, 23 Jul 2005 08:54:27 -0400), Harald
> Welte <[EMAIL PROTECTED]> says:
>
> > --- a/include/linux/netlink.h
> > +++ b/include/linux/netlink.h
> > @@ -20,7 +20,7 @@
> > #define
Linus Torvalds wrote:
On Fri, 22 Jul 2005, Lee Revell wrote:
Con's interactivity benchmark looks quite promising for finding
scheduler related interactivity regressions.
I doubt that _any_ of the regressions that are user-visible are
scheduler-related. They all tend to be disk IO
Lee Revell wrote:
On Fri, 2005-07-22 at 21:15 -0500, Alejandro Bonilla wrote:
OK, I will, but I first of all need to learn how to tell if benchmarks
are better or worse.
Con's interactivity benchmark looks quite promising for finding
scheduler related interactivity regressions. It
On Fri, 2005-07-22 at 20:31 -0700, Linus Torvalds wrote:
>
> On Fri, 22 Jul 2005, Lee Revell wrote:
> >
> > Con's interactivity benchmark looks quite promising for finding
> > scheduler related interactivity regressions.
>
> I doubt that _any_ of the regressions that are user-visible are
>
Hi.
On Fri, 2005-07-22 at 17:50, David S. Miller wrote:
> From: Nigel Cunningham <[EMAIL PROTECTED]>
> Date: Fri, 22 Jul 2005 14:11:17 +1000
>
> > In making some modifications to Suspend, we've discovered that some
> > arches use kmalloc and others use get_free_pages to allocate the stack.
> >
On Fri, 2005-07-22 at 21:15 -0500, Alejandro Bonilla wrote:
> OK, I will, but I first of all need to learn how to tell if benchmarks
> are better or worse.
Con's interactivity benchmark looks quite promising for finding
scheduler related interactivity regressions. It certainly has confirmed
Lee Revell wrote:
On Fri, 2005-07-22 at 20:07 -0500, Alejandro Bonilla wrote:
I will get flames for this, but my laptop boots faster and sometimes
responds faster in 2.4.27 than in 2.6.12. Sorry, but this is the fact
for me. IBM T42.
Sorry dude, but there's just no way that any
On Fri, 2005-07-22 at 20:07 -0500, Alejandro Bonilla wrote:
> I will get flames for this, but my laptop boots faster and sometimes
> responds faster in 2.4.27 than in 2.6.12. Sorry, but this is the fact
> for me. IBM T42.
Sorry dude, but there's just no way that any automated process can catch
In article <[EMAIL PROTECTED]> (at Sat, 23 Jul 2005 08:54:27 -0400), Harald
Welte <[EMAIL PROTECTED]> says:
> --- a/include/linux/netlink.h
> +++ b/include/linux/netlink.h
> @@ -20,7 +20,7 @@
> #define NETLINK_IP6_FW 13
> #define NETLINK_DNRTMSG 14 /* DECnet
Hi Dave,
Hi Evgeniy,
the following patch fixes the illegal use of NETLINK_NFLOG by the
1wire drivers. It assumes that the netlink tap families can now safely
be reclaimed, which is the case according to Dave at netconf'05.
I'm not sure who would be the right person to fix this, but this patch
Hi,
Does vanilla kernel 2.6.12 work for you?
It doesn't contain hpt366 driver update.
Bartlomiej
On 7/22/05, mdew <[EMAIL PROTECTED]> wrote:
> I'm unable to mount an ext2 drive using the hpt370A raid card.
>
> upon mounting the drive, dmesg will spew these errors..I've tried
> different cables
Karim Yaghmour writes:
>
> Tom Zanussi wrote:
> > - removed the deliver() callback
> > - removed the relay_commit() function
>
> This breaks LTT. Any reason why this needed to be removed? In the end,
> the code will just end up being duplicated in ltt and all other users.
> IOW, this is
Nishanth Aravamudan <[EMAIL PROTECTED]> wrote:
>
>
> +/*
> + * schedule_timeout_msecs - sleep until timeout
> + * @timeout_msecs: timeout value in milliseconds
> + *
> + * A human-time (but otherwise identical) alternative to
> + * schedule_timeout() The state, therefore, *does* need to be set
Blaisorblade wrote:
Adrian Bunk stusta.de> writes:
On Thu, Jul 21, 2005 at 09:40:43PM -0500, Alejandro Bonilla wrote:
How do we know that something is OK or wrong? just by the fact that
it works or not, it doesn't mean like is OK.
There has to be a process for any user to be able
k8 s wrote:
I AM SORRY FOR THE PREVIOUS MAIL.
I am correcting my previous mail.
Infact I see only One race(not three as was wrongly pointed out).
I commented out the section once again where the race might be.
/
Race Here . The
Tom Marshall wrote:
On Fri, Jul 22, 2005 at 08:21:25PM +0100, Paulo Marques wrote:
Tom Marshall wrote:
The patch to fix "setitimer timer expires too early" is causing issues for
the Helix server. We have a timer processs that updates the server's
timestamp on an itimer and it expects the
On Thu, 21 Jul 2005 11:21:05 -0400 (EDT), Jim Faulkner <[EMAIL PROTECTED]>
wrote:
>
>Recently I upgraded from 2.6.11.11 to 2.6.12.3. This morning I tried
>using my Zip drive... unfortunately it doesn't work under 2.6.12.3. To
>verify that this was a kernel problem, I rebooted to 2.6.11.11.
I AM SORRY FOR THE PREVIOUS MAIL.
I am correcting my previous mail.
Infact I see only One race(not three as was wrongly pointed out).
I commented out the section once again where the race might be.
On 7/23/05, k8 s <[EMAIL PROTECTED]> wrote:
> Hello,
> I see a possible race in linux-2.6.12
On 7/22/05, Jesper Juhl <[EMAIL PROTECTED]> wrote:
> On 7/21/05, Jesper Juhl <[EMAIL PROTECTED]> wrote:
> > On 7/21/05, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
> > >
> > > On Thu, 21 Jul 2005, Jesper Juhl wrote:
> > >
> > > > On 7/21/05, Kyle Moffett <[EMAIL PROTECTED]> wrote:
> > > >>
On 22.07.2005 [20:31:55 -0400], Arjan van de Ven wrote:
>
> > How does something like this look? If this looks ok, I'll send out
> > bunches of patches to add users of the new interfaces.
>
> I'd drop the FASTCALL stuff... nowadays with regparm that's automatic
> and the cost of
Hello,
I see a possible race in linux-2.6.12 ipsec code function xfrm4_rcv_encap.
I want to double check with the group.
The issue is with SMP(mostly) or Preemptible Kernels.
The race comes when someone flushes the SA's
(setkey -Fexecuting on another processor )
while xfrm_rcv_encap is executing
David Lang wrote:
On Sat, 23 Jul 2005, Blaisorblade wrote:
IMHO, I think that publishing statistics about kernel patches
downloads would
be a very Good Thing(tm) to do. Peter, what's your opinion? I think
that was
even talked about at Kernel Summit (or at least I thought of it
there), but
On Sat, 23 Jul 2005, Blaisorblade wrote:
IMHO, I think that publishing statistics about kernel patches downloads would
be a very Good Thing(tm) to do. Peter, what's your opinion? I think that was
even talked about at Kernel Summit (or at least I thought of it there), but
I've not understood if
Hi!
> > Unfortunately, if you only get printk() working after you ran
> > userspace app... well it makes debugging things like SATA
> > "interesting". So I quite like this patch.
>
> Most interesting laptop vendors have at least one model in each range
> with a serial port, which makes this sort
Adrian Bunk stusta.de> writes:
> On Thu, Jul 21, 2005 at 09:40:43PM -0500, Alejandro Bonilla wrote:
> >
> >How do we know that something is OK or wrong? just by the fact that
> > it works or not, it doesn't mean like is OK.
> >
> > There has to be a process for any user to be able to
Pavel Machek <[EMAIL PROTECTED]> wrote:
> Unfortunately, if you only get printk() working after you ran
> userspace app... well it makes debugging things like SATA
> "interesting". So I quite like this patch.
Most interesting laptop vendors have at least one model in each range
with a serial
Hi!
> swsusp now mostly works on my TP 600X. If I don't eject the pcmcia card
> (usually a prism54 wireless card), swsusp begins the process of
> hibernation, but never gets to the writing pages part. The eth0 somehow
> tries to reload the firmware (as if it's been woken up), and then
>
> How does something like this look? If this looks ok, I'll send out
> bunches of patches to add users of the new interfaces.
I'd drop the FASTCALL stuff... nowadays with regparm that's automatic
and the cost of register-vs-stack isn't too big anyway
Also I'd rather not add the non-msec
Hi!
> > Without this patch my laptop fails to resume from suspend to RAM...
> >
> > It applies against a pretty recent 2.6.13-rc3 from git..
> >
>
> Hi,
>
> Is it necessary to do free_irq for suspend? Shouldn't disable_irq
> be enough?
Due to recent changes in ACPI, yes, it is neccessary.
Hi!
> > At OLS at lot of people were giving out about cards not resuming,
> > so using a patch from Michael Marineau and help from lots of people
> > sitting around in a circle at OLS I've gotten a patch that restores video
> > on my laptop by going into real mode and re-posting the BIOS
This adds support for touchscreen on Sharp Zaurus sl-5500. Vojtech,
please apply,
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
diff --git a/drivers/input/touchscreen/Kconfig
b/drivers/input/touchscreen/Kconfig
--- a/drivers/input/touchscreen/Kconfig
+++ b/drivers/input/touchscreen/Kconfig
@@
On 08.07.2005 [16:08:24 -0700], Andrew Morton wrote:
> [EMAIL PROTECTED] wrote:
> >
> > @@ -655,7 +655,7 @@ i2QueueCommands(int type, i2ChanStrPtr p
> > timeout--; // So negative values == forever
> >
> > if (!in_interrupt()) {
>
> I worry about what
> > actually, let me also say that CKRM is on a continuum that includes
> > current (global) /proc tuning for various subsystems, ulimits, and
> > at the other end, Xen/VMM's. it's conceivable that CKRM could wind up
> > being useful and fast enough to subsume the current global and per-proc
>
swsusp now mostly works on my TP 600X. If I don't eject the pcmcia card
(usually a prism54 wireless card), swsusp begins the process of
hibernation, but never gets to the writing pages part. The eth0 somehow
tries to reload the firmware (as if it's been woken up), and then
everything hangs. If
On Fri, 22 Jul 2005, linux-os (Dick Johnson) wrote:
> Seems to be readable and starts with 'ELF'. It's something the the 'C'
> runtime may library use to make syscalls to the kernel. Older libraries
> used interrupt 0x80, newer ones may use this. Roland McGrath has made
> patches to this segment
Roger Heflin wrote:
I have seen RH3.0 crash on 32GB systems because it has too
much memory tied up in write cache. It required update 2
(this was a while ago) and a change of a parameter in /proc
to prevent the crash, it was because of a overagressive
write caching change RH implemented in
Tom Zanussi wrote:
> - removed the deliver() callback
> - removed the relay_commit() function
This breaks LTT. Any reason why this needed to be removed? In the end,
the code will just end up being duplicated in ltt and all other users.
IOW, this is not some potential future use, but something
On Thu, Jul 21, 2005 at 09:40:43PM -0500, Alejandro Bonilla wrote:
>...
>How does one check if hotplug is working better than before? How do
> I test the fact that a performance issue seen in the driver is now fixed
> for me or most of users? How do I get back to a bugzilla and tell that
>
On Thu, 21 Jul 2005, Chuck Ebbert wrote:
>
> This patch makes restore_fpu() an inline. When L1/L2 cache are saturated
> it makes a measurable difference.
I've now pushed out an alternative fix for this, which imho is much
cleaner.
We've long had infrastructure for "alternative asm
Arjan, Alan:
I didn't know that dmraid supports MegaIDE nowadays. Thanks for the
tipoff, and I apologize for the unnecessary traffic. I'll look into dmraid.
--D
Alan Cox wrote:
> On Iau, 2005-07-21 at 15:37 -0700, Darrick J. Wong wrote:
>
>>I've noticed what might be a small bug with the
Dave Airlie <[EMAIL PROTECTED]> wrote:
> At OLS at lot of people were giving out about cards not resuming,
> so using a patch from Michael Marineau and help from lots of people
> sitting around in a circle at OLS I've gotten a patch that restores video
> on my laptop by going into real mode
On Friday 22 July 2005 17:33, Dave Airlie wrote:
>
> Without this patch my laptop fails to resume from suspend to RAM...
>
> It applies against a pretty recent 2.6.13-rc3 from git..
>
Hi,
Is it necessary to do free_irq for suspend? Shouldn't disable_irq
be enough?
--
Dmitry
-
To unsubscribe
On Fri, Jul 22, 2005 at 03:34:09AM +0200, Martin MOKREJ? wrote:
> Hi,
Hi Martin,
> I think the discussion going on here in another thread about lack
> of positive information on how many testers successfully tested certain
> kernel version can be easily solved with real solution.
>
> How
On Fri, Jul 22, 2005 at 11:18:13PM +0200, Olaf Dietsche wrote:
> Sam Ravnborg <[EMAIL PROTECTED]> writes:
>
> > +obj-$(CONFIG_VIDEO_DEV) := video/
> > +obj-$(CONFIG_VIDEO_DEV) := radio/
>
> s/VIDEO/RADIO/
If you look at drivers/media/radio/Kconfig you will see that the above
is coorect. Thre
Without this patch my laptop fails to resume from suspend to RAM...
It applies against a pretty recent 2.6.13-rc3 from git..
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG
diff --git
This patch fixes the following warnings with -Wundef:
<-- snip -->
...
CC drivers/block/sx8.o
drivers/block/sx8.c:1585:5: warning: "IF_64BIT_DMA_IS_POSSIBLE" is not defined
drivers/block/sx8.c:1604:5: warning: "IF_64BIT_DMA_IS_POSSIBLE" is not defined
...
<-- snip -->
Wouldn't having (practically) all your memory used for cache slow down
starting a new program? First it would have to free up that space, and then
put stuff in that space, taking potentially twice as long. I think there
should be a system call for freeing cached memory, for those that do want to
This patch fixes the following warnings with -Wundef:
<-- snip -->
...
CC drivers/ieee1394/sbp2.o
drivers/ieee1394/sbp2.c:202:5: warning: "CONFIG_IEEE1394_SBP2_DEBUG" is not
defined
drivers/ieee1394/sbp2.c:207:7: warning: "CONFIG_IEEE1394_SBP2_DEBUG" is not
defined
This patch fixes the following warnings with -Wundef:
<-- snip -->
...
CC drivers/char/rio/rioboot.o
drivers/char/rio/rioboot.c:905:5: warning: "NEED_TO_FIX" is not defined
drivers/char/rio/rioboot.c:921:5: warning: "NEED_TO_FIX" is not defined
drivers/char/rio/rioboot.c:1146:5:
This patch fixes the following warning with -Wundef:
<-- snip -->
...
CC drivers/net/ne.o
drivers/net/ne.c:134:7: warning: "CONFIG_PLAT_OAKS32R" is not defined
...
<-- snip -->
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.13-rc3-mm1-full/drivers/net/ne.c.old
This patch fixes the following warnings with -Wundef:
<-- snip -->
...
CC drivers/cdrom/mcdx.o
drivers/cdrom/mcdx.c:54:5: warning: "RCS" is not defined
...
drivers/cdrom/mcdx.c:709:5: warning: "FALLBACK" is not defined
drivers/cdrom/mcdx.c:1219:5: warning: "WE_KNOW_WHY" is not defined
On Gwe, 2005-07-22 at 13:00 -0300, Vinicius wrote:
>I also read on the Linux-Kernel that the problem may be related to an
> exhaustion of your kernels address space, I read that the hugemem-kernel
> might be the solution to this case since it has 4GB for the kernel memory
> plus 4GB for
-Wundef found an (although perhaps harmless) bug:
<-- snip -->
...
CC net/ieee80211/ieee80211_crypt.o
In file included from net/ieee80211/ieee80211_crypt.c:21:
include/net/ieee80211.h:26:5: warning: "WIRELESS_EXT" is not defined
CC net/ieee80211/ieee80211_crypt_wep.o
In file
This patch fixes the following warning with -Wundef:
<-- snip -->
...
CC drivers/isdn/hisax/l3dss1.o
drivers/isdn/hisax/l3dss1.c:356:5: warning: "HISAX_DE_AOC" is not defined
...
<-- snip -->
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
--- linux-2.6.13-rc3-mm1-full/include/linux/ftape.h.old 2005-07-22
18:17:18.0 +0200
+++ linux-2.6.13-rc3-mm1-full/include/linux/ftape.h 2005-07-22
18:17:41.0 +0200
@@ -165,7 +165,7 @@
# undef CONFIG_FT_FDC_DMA
# define
This patch fixes the following warnings with -Wundef:
<-- snip -->
...
CC drivers/char/drm/drm_pci.o
drivers/char/drm/drm_pci.c:53:5: warning: "DRM_DEBUG_MEMORY" is not defined
drivers/char/drm/drm_pci.c:84:5: warning: "DRM_DEBUG_MEMORY" is not defined
drivers/char/drm/drm_pci.c:119:5:
On Fri, Jul 22, 2005 at 04:18:46PM -0500, Davy Durham wrote:
> Please forgive and redirect me if this is not the right place to ask
> this question:
>
> I'm looking to write a sort of messaging system that would take input
> from any number of entities that "register" with it.. it would then
>
Sam Ravnborg <[EMAIL PROTECTED]> writes:
> +obj-$(CONFIG_VIDEO_DEV) := video/
> +obj-$(CONFIG_VIDEO_DEV) := radio/
s/VIDEO/RADIO/
Regards, Olaf.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Please forgive and redirect me if this is not the right place to ask
this question:
I'm looking to write a sort of messaging system that would take input
from any number of entities that "register" with it.. it would then
route the messages to outputs and so forth..
I'm guessing that the
On Fri, Jul 15, 2005 at 01:36:53AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.13-rc2-mm2:
>...
> +ckrm-rule-based-classification-engine-full-ce.patch
>...
> Class-based kernel resource management
>...
This patch fixes the following warning with -Wundef:
<-- snip -->
...
CC
Adrian Bunk wrote:
On Fri, Jul 22, 2005 at 07:55:48PM +0100, christos gentsis wrote:
hello
Hi Chris,
i would like to ask if it possible to change the optimization of the
kernel from -O2 to -O3 :D, how can i do that? if i change it to the top
level Makefile does it change to
I started looking at this driver after seeing the following warnings
with -Wundef:
<-- snip -->
...
CC drivers/net/8139too.o
drivers/net/8139too.c:1961:5: warning: "RTL8139_DEBUG" is not defined
drivers/net/8139too.c:2047:5: warning: "RTL8139_DEBUG" is not defined
...
<-- snip -->
The SCSI qlogicisp driver is both marked BROKEN and superseded by the
qla1280 driver.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
Due to it's size, the patch is attached compressed.
Documentation/scsi/00-INDEX |2
Documentation/scsi/qlogicfas.txt |3
Really appreciate that, is roland mcgrath listening? what's his email ID?
On 7/23/05, linux-os (Dick Johnson) <[EMAIL PROTECTED]> wrote:
>
> On Fri, 22 Jul 2005, vamsi krishna wrote:
>
> > Hi,
> >
> >> It doesn't. The 32-bit machines never show 64 bit words in
> >> /proc/NN/maps. They don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernd Eckenfels wrote:
> On Fri, Jul 22, 2005 at 01:00:18PM +0200, Stefan Smietanowski wrote:
>
>>>You cant have 16GB of Memory with 32bit CPUs.
>>
>>PAE
>>CONFIG_HIGMEM64G
>>Supports a 36bit address space, which Xeons do support.
>
>
> Yes right,
On Fri, Jul 22, 2005 at 08:21:25PM +0100, Paulo Marques wrote:
> Tom Marshall wrote:
> >The patch to fix "setitimer timer expires too early" is causing issues for
> >the Helix server. We have a timer processs that updates the server's
> >timestamp on an itimer and it expects the signal to be
I have seen RH3.0 crash on 32GB systems because it has too
much memory tied up in write cache. It required update 2
(this was a while ago) and a change of a parameter in /proc
to prevent the crash, it was because of a overagressive
write caching change RH implemented in the kernel resulted
in
Tom Zanussi writes:
>
> OK, if we got rid of the padding counts and commit counts and let the
> client manage those, we can simplify the buffer switch slow path and
> make the API simpler in the process. Here's a first proposal for
> doing that - I won't know until I actually do it what
Tom Zanussi writes:
>
> OK, if we got rid of the padding counts and commit counts and let the
> client manage those, we can simplify the buffer switch slow path and
> make the API simpler in the process. Here's a first proposal for
> doing that - I won't know until I actually do it what
On Fri, Jul 22, 2005 at 01:01:32PM -0700, Paul Jackson wrote:
> Another vote in favor of relayfs here ...
At OLS the 'SystemTAP' idea was presented, which has been partially
implemented already, and it builds on relayfs as well. It dovetails nicely
with kprobes.
So it appears there is a sizeable
On 7/22/05, Sam Ravnborg <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 22, 2005 at 12:12:12PM -0500, Patrick Draper wrote:
> > Why isn't a code formatting program used? People could write the code
> > as they like to write it, then format it automatically in a standard
> > way before it gets put into
On Fri, 2005-07-22 at 12:35 -0400, Mark Hahn wrote:
> actually, let me also say that CKRM is on a continuum that includes
> current (global) /proc tuning for various subsystems, ulimits, and
> at the other end, Xen/VMM's. it's conceivable that CKRM could wind up
> being useful and fast enough
>From my previous message on this subject:
> With 2.6.13-rc3 I now get these errors (2.6.11.4 was fine) on my TP
> 600X (Debian 'etch' system):
>
> localhost kernel: hda: dma_timer_expiry: dma status == 0x21
> localhost kernel: hda: DMA timeout error
> localhost kernel: hda: dma timeout error:
On Fri, Jul 22, 2005 at 12:52:22PM -0700, David Lang wrote:
> This is a airly frequent question
>
> the short answer is 'don't try'
>
> the longer answer is that all the additional optimization options that are
> part of O3+ are considered individually and if they make sense for the
> kernel
On Fri, Jul 22, 2005 at 07:55:48PM +0100, christos gentsis wrote:
> hello
Hi Chris,
> i would like to ask if it possible to change the optimization of the
> kernel from -O2 to -O3 :D, how can i do that? if i change it to the top
> level Makefile does it change to all the Makefiles?
search
From: Steve French <[EMAIL PROTECTED]>
Date: 22 Jul 2005 14:56:59 -0500
> Noticing that the loopback device (at least on RHEL4) has an unfortunate
> mtu size 16384 (which is about 50 bytes too small for SMB read
> responses), I did try increasing the MTU slightly. Changing that to
> 18000 did
On Fri, 2005-07-22 at 14:56, Steve French wrote:
> I am seeing odd tcp characteristics on the loopback device.
Although probably not related ... I thought it worth mentioning that
ethereal claims bad tcp checksum on the 2nd of each pair of tcp response
frames (the smaller one) when run on the
Another vote in favor of relayfs here ...
I am reminded by my good colleagues at SGI that relayfs is a key
to the Linux Trace Toolkit (LTT), which is in turn an important
technology for some product(s) on which SGI is working.
It is uses such as this which speak to the value of including
relayfs
I am seeing odd tcp characteristics on the loopback device.
In analyzing cifs read performance to samba, I see a fairly consistent
pattern.
TCP frame containing SMBRead request (asking for size 16K)
1st 16K of SMB Read Response (1 ms later or less) sent from samba
Samba's response is
On Fri, Jul 22, 2005 at 07:34:38PM +0530, Milind Dumbare wrote:
> Hi,
>
> LinSysSoft Technologies has taken up the challenge to incorporate
> Checkpoint and Block Level Incremental Backup (BLIB) support in the open
> source's Ext3 File System, which is very well known for its stability,
>
Shailabh wrote:
> So if the current CPU controller
> implementation is considered too intrusive/unacceptable, it can be
> reworked or (and we certainly hope not) even rejected in perpetuity.
It is certainly reasonable that you would hope such.
But this hypothetical possibility concerns me a
This is a airly frequent question
the short answer is 'don't try'
the longer answer is that all the additional optimization options that are
part of O3+ are considered individually and if they make sense for the
kernel they are explicitly enabled (in some cases the optimizations need
to be
Neil Horman wrote:
On Fri, Jul 22, 2005 at 11:32:52AM -0300, Márcio Oliveira wrote:
Neil Horman wrote:
On Thu, Jul 21, 2005 at 10:40:54AM -0300, Márcio Oliveira wrote:
http://people.redhat.com/nhorman/papers/rhel3_vm.pdf
I wrote this with norm awhile back. It may help you
Francois Romieu wrote:
Daniel Higgins <[EMAIL PROTECTED]> :
[napi for natsemi]
Can you please fill a bugzilla entry for it at bugzilla.kernel.org ?
It is bugzilla, not featurewishzilla. If some external patches
cause problem I suggest to contact their authors.
-
To unsubscribe from this list:
> Supermount is obsolete there are other tools in userspace that do the
> job perfectly.
> e.g ivman which uses hal and dbus.
They cannot mount on demand, thus cannot do the same job. The boot
partition, for example, is something that should only be mounted when
required. The same obviously also
On Fri, 22 Jul 2005, vamsi krishna wrote:
> Hi,
>
>> It doesn't. The 32-bit machines never show 64 bit words in
>> /proc/NN/maps. They don't "know" how.
>>
>> b7fd6000-b7fd7000 rw-p b7fd6000 00:00 0
>> b7ff5000-b7ff6000 rw-p b7ff5000 00:00 0
>> bffe1000-bfff6000 rw-p bffe1000 00:00 0
Daniel Higgins <[EMAIL PROTECTED]> :
[napi for natsemi]
Can you please fill a bugzilla entry for it at bugzilla.kernel.org ?
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Tom Marshall wrote:
The patch to fix "setitimer timer expires too early" is causing issues for
the Helix server. We have a timer processs that updates the server's
timestamp on an itimer and it expects the signal to be delivered at roughly
the interval retrieved from getitimer. This is very
On Fri, Jul 22, 2005 at 11:32:52AM -0300, Márcio Oliveira wrote:
> Neil Horman wrote:
>
> >On Thu, Jul 21, 2005 at 10:40:54AM -0300, Márcio Oliveira wrote:
> >
> >
> >>>http://people.redhat.com/nhorman/papers/rhel3_vm.pdf
> >>>I wrote this with norm awhile back. It may help you out.
>
On Gwe, 2005-07-22 at 12:35 -0400, Mark Hahn wrote:
> I imagine you, like me, are currently sitting in the Xen talk,
Out by a few thousand miles ;)
> and I don't believe they are or will do anything so dumb as to throw away
> or lose information. yes, in principle, the logic will need to be
1 - 100 of 414 matches
Mail list logo
