From: "Steven Rostedt (Google)"
[ Upstream commit b81e03a24966dca0b119eff0549a4e44befff419 ]
As all the subbuffer order (subbuffer sizes) must be the same throughout
the ring buffer, check the order of the buffers that are doing a CPU
buffer swap in ring_buffer_swap_cpu() to make sure they are t
From: "Steven Rostedt (Google)"
As all the subbuffer order (subbuffer sizes) must be the same throughout
the ring buffer, check the order of the buffers that are doing a CPU
buffer swap in ring_buffer_swap_cpu() to make sure they are the same.
If the are not the same, then fail to do the swap, o
From: "Steven Rostedt (Google)"
As all the subbuffer order (subbuffer sizes) must be the same throughout
the ring buffer, check the order of the buffers that are doing a CPU
buffer swap in ring_buffer_swap_cpu() to make sure they are the same.
If the are not the same, then fail to do the swap, o
From: "Steven Rostedt (Google)"
As all the subbuffer order (subbuffer sizes) must be the same throughout
the ring buffer, check the order of the buffers that are doing a CPU
buffer swap in ring_buffer_swap_cpu() to make sure they are the same.
If the are not the same, then fail to do the swap, o
From: "Steven Rostedt (Google)"
As all the subbuffer order (subbuffer sizes) must be the same throughout
the ring buffer, check the order of the buffers that are doing a CPU
buffer swap in ring_buffer_swap_cpu() to make sure they are the same.
If the are not the same, then fail to do the swap, o
I think we tracked it down to the "eptad" kernel option on Broadwell processors.
Setting "kvm-intel.eptad=0" turned it off.
Chris
On 11/20/2017 03:07 AM, Huaitong Han wrote:
Hi, Chris
I have met the same issue too, did you have found out the root cause ?
Thanks a lot.
Huaitong Han
2016-1
Hi, Chris
I have met the same issue too, did you have found out the root cause ?
Thanks a lot.
Huaitong Han
2016-10-12 0:02 GMT+08:00 Chris Friesen :
> On 10/08/2016 02:05 AM, Hillf Danton wrote:
>>
>> On Friday, October 07, 2016 5:01 AM Chris Friesen
>>>
>>>
>>> I have Linux host running as a
On 10/08/2016 02:05 AM, Hillf Danton wrote:
On Friday, October 07, 2016 5:01 AM Chris Friesen
I have Linux host running as a kvm hypervisor. It's running CentOS. (So the
kernel is based on 3.10 but with loads of stuff backported by RedHat.) I
realize this is not a mainline kernel, but I was
On Friday, October 07, 2016 5:01 AM Chris Friesen
>
> I have Linux host running as a kvm hypervisor. It's running CentOS. (So the
> kernel is based on 3.10 but with loads of stuff backported by RedHat.) I
> realize this is not a mainline kernel, but I was wondering if anyone is aware
> of
> si
I have Linux host running as a kvm hypervisor. It's running CentOS. (So the
kernel is based on 3.10 but with loads of stuff backported by RedHat.) I
realize this is not a mainline kernel, but I was wondering if anyone is aware of
similar issues that had been fixed in mainline.
When doing
If system have no swap device, scan_control's may_swap field have to
be set to zero.
This patch will remove redundant calc_reclaim_mapped call which called
in shrink_active_list by sc->may_swap.
This patch is made from 2.6.24-rc6-mm1.
Signed-off-by: minchan kim <[EMAIL PROTECTE
>> When this is sorted out, should I keep the previous patch [1] applied
>> as well?
>
> That doesn't hurt.
OK, I've used just the latter patch (because I somehow believe the first
one lowers the probability of bad behavior), so let's see if kswapd
consumes CPU again. I don't have any test patter
On Wed, 26 Sep 2007 09:27:36 +0200
Jan Kundrát <[EMAIL PROTECTED]> wrote:
> Rik van Riel wrote:
> > Could you try out the attached patch, too?
>
> Sorry, I wasn't able to apply it against 2.6.22-gentoo-r3 and vanilla
> 2.6.22.7; I don't have the "order" member in the "struct scan_control"
> and a
Rik van Riel wrote:
> Could you try out the attached patch, too?
Sorry, I wasn't able to apply it against 2.6.22-gentoo-r3 and vanilla
2.6.22.7; I don't have the "order" member in the "struct scan_control"
and also the bit about "if (sync_writeback == PAGEOUT_IO_SYNC &&
may_enter_fs)" was missing
On Tue, 25 Sep 2007 12:13:41 +0200
Jan Kundrát <[EMAIL PROTECTED]> wrote:
> Rik van Riel wrote:
> > How much memory did you have in "cached" when you looked
> > with top (and no swap enabled) ?
>
> Hi Rik,
> it was pretty low number (several thousands, or
Rik van Riel wrote:
> How much memory did you have in "cached" when you looked
> with top (and no swap enabled) ?
Hi Rik,
it was pretty low number (several thousands, or maybe tens of thousands).
In the meanwhile, I've come across your patch [1] ("prevent kswapd from
fr
l SATA
> disk, and I have 1GB of RAM and no swap.
>
> After several suspend to RAM/resume cycles, the X interface got pretty
> slow today. Looking at the top output, I see that one core was
> completely busy in the "wa" state and according to `ps auxww`, the
> kswapd0 pro
Hi folks,
I use a 2.6.22-gentoo-r2 SMP kernel with fglrx 8.40.4 [1], tp_smapi-0.32
and ipw3945-1.2.0 on a Thinkpad T60 with dual core Intel Core CPU. My
root filesystem is XFS stored on an internal SATA disk, and I have 1GB
of RAM and no swap.
After several suspend to RAM/resume cycles, the X
Hello,
I am experiencing oopses when using tmpfs heavily on an embedded
Au1550-based board (MIPS 32-bit core, little-endian, 128MB RAM).
Everything I need seemed to work (PCI, USB, JFFS2, busybox, tools like
mtools, WLAN, network, ...). The system currently uses busybox-1.00 and
glibc
I ran LTP on a 512MB i386 UP nfsroot test system with no swap with
2.6.21-rc7-git6
It deadlocked during the LTP run with no progress anymore and
ssh remote login not working anymore:
<<>>
mmap001 0 INFO : mmap()ing file of 1 pages or 4096 bytes
mmap001 1 P
On 2/14/07, Thibaud Hulin <[EMAIL PROTECTED]> wrote:
Hi !
distro related: check
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/66637 and
all the duplicates
After compiling the kernel, I discover that my computer don't use the swap.
So, I try a cat .config |grep SW, and I got :
CO
Hi !
After compiling the kernel, I discover that my computer don't use the swap.
So, I try a cat .config |grep SW, and I got :
CONFIG_SWAP=y
# CONFIG_X86_VISWS is not set
CONFIG_X86_BSWAP=y
CONFIG_SUSPEND2_SWAP=y
CONFIG_SUSPEND2_REPLACE_SWSUSP=y
# CONFIG_AGP_SWORKS is not set
CONFIG_USB_AUERSWALD
Thanks Andrew - you're right. Drop this patch in /dev/null.
* I will look around for some way that user code can
detect that a task has provoked swapping, or propose
a small patch, perhaps to /proc, for that, if need be.
* I agree that the action, killing a task or whatever, can
and s
This machine has no swap at all.
The oops was hand-copied.
--
Kurt Huwig iKu Systemhaus AGhttp://www.iku-ag.de/
Vorstand Am Römerkastell 4Telefon 0681/96751-0
66121 SaarbrückenTelefax 0681/96751-66
GnuPG 1024D/99DD9468 64B1
Interesting comments, Andrew. Thanks
It will likely be a couple of days before
I respond to them. I suspect a couple
of us SGI folks should powwow first.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EM
Paul Jackson <[EMAIL PROTECTED]> wrote:
>
> This mechanisms differs from a general purpose out-of-memory
> killer in various ways, including:
>
> * An oom-killer tries to score the bad buy, to avoid shooting
> the innocent little task that just happened to ask for one
> page too many.
>
Question:
Should I call oom_kill_process(), oom_kill_task(),
or __oom_kill_task(), when the current task decides
that it is better to die than to swap, so calls the
routine mm/oom_kill.c:oom_attempt_suicide() that this
patch adds, below?
My best gue
7, 2005 4:28 AM
To: linux-kernel@vger.kernel.org
Cc: Guy; 'Mike Hardy'; 'Jesper Juhl'; linux-raid@vger.kernel.org;
[EMAIL PROTECTED]
Subject: Re: No swap can be dangerous (was Re: swap on RAID (was Re: swp -
Re: ext3 journal on software raid))
On Thursday 06 January 2005 23:15,
28 matches
Mail list logo
