Denys Vlasenko writes:
> Signed-off-by: Denys Vlasenko
> CC: lgu...@lists.ozlabs.org
> CC: x...@kernel.org
> CC: linux-kernel@vger.kernel.org
Oh, thanks, applied!
And now it's down to one instruction, we could change
try_deliver_interrupt() to handle this case (rather than ignoring the
interrup
Currently, for cgroup writeback, the IO submission paths directly
associate the bio's with the blkcg from inode_to_wb_blkcg_css();
however, it'd be necessary to keep more writeback context to implement
foreign inode writeback detection. wbc (writeback_control) is the
natural fit for the extra cont
cancel_dirty_page() currently performs TestClearPageDirty() and then
tests whether the mapping exists and has cap_account_dirty. This
patch swaps the order so that it performs the mapping tests first.
If the mapping tests fail, the dirty is cleared with ClearPageDirty().
The order or the conditio
Hi Dave,
Thank you for letting us know. Since we are not an expert of XFS (nor
want to be), we really want to let you guys know it's potential bug
that you might miss (we are helping you!). And that's why Sanidhya
asked (rather than sending a patch) at the first place.
I agree that the comment is
It is just an optimization. We don't need the value of status variable
if the packet is filtered.
Signed-off-by: Alexander Drozdov
---
net/packet/af_packet.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/net/packet/af_packet.c b/net/packet/af_packet.c
index f8db706..
Introduce TP_STATUS_CSUM_VALID tp_status flag to tell the
af_packet user that at least the transport header checksum
has been already validated.
For now, the flag may be set for incoming packets only.
Signed-off-by: Alexander Drozdov
Cc: Willem de Bruijn
---
Documentation/networking/packet_mma
Hi Guenter,
Adding LKML to Cc.
On Sun, Mar 22, 2015 at 10:50:28PM -0700, Guenter Roeck wrote:
> On 03/22/2015 10:33 PM, Baruch Siach wrote:
> >+wdt->restart_handler.notifier_call = dc_restart_handler;
> >+wdt->restart_handler.priority = 128;
>
> Is 128 intentional
On 2015/3/20 16:38, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 7486341a98f26857f383aec88ffa10950087c3a1 ("x86/platform, acpi: Bypass
> legacy PIC and PIT in ACPI hardware reduced mode")
>
>
> +---
There is no check for udf_tgetblk(), which could return NULL, in udf_symlink().
So there is a possibility of returning NULL under heavy memory pressure and
possibility of NULL dereference.
Signed-off-by: Changwoo Min
---
fs/udf/namei.c | 4
1 file changed, 4 insertions(+)
diff --git a/f
Currently perf kmem shows total (page) allocation stat by default, but
sometimes one might want to see live (total alloc-only) requests/pages
only. The new --live option does this by subtracting freed allocation
from the stat.
Signed-off-by: Namhyung Kim
---
tools/perf/Documentation/perf-kmem.t
Hello,
Currently perf kmem command only analyzes SLAB memory allocation. And
I'd like to introduce page allocation analysis also. Users can use
--slab and/or --page option to select it. If none of these options
are used, it does slab allocation analysis for backward compatibility.
* changes
Add new sort keys for page: page, order, mtype, gfp - existing
'bytes', 'hit' and 'callsite' sort keys also work for page. Note that
-s/--sort option should be preceded by either of --slab or --page
option to determine where the sort keys applies.
Now it properly groups and sorts allocation stats
The perf kmem command records and analyze kernel memory allocation
only for SLAB objects. This patch implement a simple page allocator
analyzer using kmem:mm_page_alloc and kmem:mm_page_free events.
It adds two new options of --slab and --page. The --slab option is
for analyzing SLAB allocator a
Like perf stat, this makes easy to read the numbers on stat like below:
# perf kmem stat
SUMMARY
===
Total bytes requested: 9,770,900
Total bytes allocated: 9,782,712
Total bytes wasted on internal fragmentation: 11,812
Internal fragmentation: 0.120744%
Cross CPU allocations:
It perf kmem support caller statistics for page. Unlike slab case,
the tracepoints in page allocator don't provide callsite info. So
it records with callchain and extracts callsite info.
Note that the callchain contains several memory allocation functions
which has no meaning for users. So skip
401 - 415 of 415 matches
Mail list logo