twitter: linux.kernel - 26 new messages in 17 topics

linux.kernel
http://groups.google.com/group/linux.kernel?hl=en

Today's topics:

* RFC directio: partial writes support - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/5f95397237af6d75?hl=en
* x86: Fix sched_clock_cpu for systems with unsynchronized TSC - 1 messages, 1
author
http://groups.google.com/group/linux.kernel/t/ad0d6572aea6fa62?hl=en
* : Sparc - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/4ae267884de82c2c?hl=en
* i2c updates for 2.6.34, round 1 - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/7b7f85629f7a9634?hl=en
* [4/4] SLAB: Fix node add timer race in cache_reap - 2 messages, 1 author
http://groups.google.com/group/linux.kernel/t/a8beda1232363b5e?hl=en
* usbaudio: Fix wrong bitrate for Creative Creative VF0470 Live Cam - 1
messages, 1 author
http://groups.google.com/group/linux.kernel/t/829b9e9d076b418c?hl=en
* memcg: dirty pages accounting and limiting infrastructure - 5 messages, 3
authors
http://groups.google.com/group/linux.kernel/t/98b8f3d66410be44?hl=en
* perf_events: add sampling period randomization support - 1 messages, 1
author
http://groups.google.com/group/linux.kernel/t/54108222cc877582?hl=en
* do_loop_readv_writev() not as described for drivers implementing only write()
? - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/1cb0b5d5d3ba8758?hl=en
* Panic at tcp_xmit_retransmit_queue - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/75f63e704505ce49?hl=en
* rcu: suppress RCU lockdep warnings during early boot - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/793bcd4fc844361a?hl=en
* sparc: use asm-generic/scatterlist.h - 4 messages, 3 authors
http://groups.google.com/group/linux.kernel/t/18cde759295738d0?hl=en
* Staging: IIO: Fix uses of spinlocks prior to init in ring implementations -
1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/6dae3730fb254190?hl=en
* serial: Add OMAP high-speed UART driver. - 2 messages, 2 authors
http://groups.google.com/group/linux.kernel/t/367b898833e91d7d?hl=en
* Question about policy of calling lockdep functions in trylocks - 1 messages,
1 author
http://groups.google.com/group/linux.kernel/t/7ad22c2c3d4c9155?hl=en
* kmemleak for MIPS - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/91ce29e0eba5d9e1?hl=en
* yaffs2 NAND fs - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/1b91501080fbaa7f?hl=en

==============================================================================
TOPIC: RFC directio: partial writes support
http://groups.google.com/group/linux.kernel/t/5f95397237af6d75?hl=en
==============================================================================

== 1 of 1 ==
Date: Tues, Mar 2 2010 4:40 am
From: Nick Piggin

On Tue, Mar 02, 2010 at 12:34:06PM +0100, Jan Kara wrote:
> On Tue 02-03-10 20:25:02, Nick Piggin wrote:
> > On Mon, Mar 01, 2010 at 03:21:49PM -0800, Andrew Morton wrote:
> > > On Thu, 25 Feb 2010 15:45:58 +0300
> > > Dmitry Monakhov <dmonakhov@openvz.org> wrote:
> > >
> > > > Can someone please describe me why directio deny partial writes.
> > > > For example if someone try to write 100Mb but file system has less
> > > > data it return ENOSPC in the middle of block allocation.
> > > > All allocated blocks will be truncated (it may be 100Mb -4k) end
> > > > ENOSPC will be returned. As far as i remember direct_io always act
> > > > like this, but i never asked why?
> > > > Why do we have to give up all the progress we made?
> > > > In fact partial writes are possible in case of holes, when we
> > > > fall back to buffered write. XFS implemented partial writes.
> > >
> > > The problem with direct-io writes is that the writes don't necessarily
> > > complete in file-offset-ascending order. So if we've issued 50 write
> > > BIOs and then hit an EIO on a BIO then we could have a hunk of
> > > unwritten data with newly-writted data either side of it. If we get a
> > > bunch of discontiguous EIO BIOs coming in then the problem gets even
> > > messier - we have a span of disk which has a random mix of
> > > correctly-written and not-correctly-written runs of sectors. What do
> > > we do with that?
> >
> > Hmm, what if we're filling in a hole with direct IO? I don't see where
> > blocks allocated in DIO code will be trimmed on a failed write (because
> > it's within isize). This could cause uninitalized data of the block to
> > leak couldn't it?
> The trick is that blockdev_direct_IO is defined to pass
> DIO_SKIP_HOLES to __blockdev_direct_IO. Thus e.g. ext2 or ext3 will just
> fail the direct IO if there is a hole and we fall back to buffered IO
> which should handle that just fine.

OK yes I see, I missed that.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

==============================================================================
TOPIC: x86: Fix sched_clock_cpu for systems with unsynchronized TSC
http://groups.google.com/group/linux.kernel/t/ad0d6572aea6fa62?hl=en
==============================================================================

== 1 of 1 ==
Date: Tues, Mar 2 2010 4:50 am
From: tip-bot for Dimitri Sivanich

Commit-ID: 14be1f7454ea96ee614467a49cf018a1a383b189
Gitweb: http://git.kernel.org/tip/14be1f7454ea96ee614467a49cf018a1a383b189
Author: Dimitri Sivanich <sivanich@sgi.com>
AuthorDate: Mon, 1 Mar 2010 11:48:15 -0600
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Tue, 2 Mar 2010 13:36:11 +0100

x86: Fix sched_clock_cpu for systems with unsynchronized TSC

On UV systems, the TSC is not synchronized across blades. The
sched_clock_cpu() function is returning values that can go
backwards (I've seen as much as 8 seconds) when switching
between cpus.

As each cpu comes up, early_init_intel() will currently set the
sched_clock_stable flag true. When mark_tsc_unstable() runs, it
clears the flag, but this only occurs once (the first time a cpu
comes up whose TSC is not synchronized with cpu 0). After this,
early_init_intel() will set the flag again as the next cpu comes
up.

Only set sched_clock_stable if tsc has not been marked unstable.

Signed-off-by: Dimitri Sivanich <sivanich@sgi.com>
Acked-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <20100301174815.GC8224@sgi.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
arch/x86/kernel/cpu/intel.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
index 879666f..7e1cca1 100644
--- a/arch/x86/kernel/cpu/intel.c
+++ b/arch/x86/kernel/cpu/intel.c
@@ -70,7 +70,8 @@ static void __cpuinit early_init_intel(struct cpuinfo_x86 *c)
if (c->x86_power & (1 << 8)) {
set_cpu_cap(c, X86_FEATURE_CONSTANT_TSC);
set_cpu_cap(c, X86_FEATURE_NONSTOP_TSC);
- sched_clock_stable = 1;
+ if (!check_tsc_unstable())
+ sched_clock_stable = 1;
}

/*
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

==============================================================================
TOPIC: : Sparc
http://groups.google.com/group/linux.kernel/t/4ae267884de82c2c?hl=en
==============================================================================

== 1 of 1 ==
Date: Tues, Mar 2 2010 4:50 am
From: David Miller

Nothing really exciting for sparc this time around.

Several cleanups, a new PCI ID for a frambuffer driver, creation
of PCI slot objects when possible, and some debugging enhancements
by supporting exception-table sysctl like powerpc and x86 do.

Please pull, thanks a lot!

The following changes since commit baac35c4155a8aa826c70acee6553368ca5243a2:
Xiaotian Feng (1):
security: fix error return path in ima_inode_alloc

are available in the git repository at:

master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-next-2.6.git master

Akinobu Mita (1):
sparc: use __ratelimit

Ben Hutchings (1):
sunxvr500: Additional PCI id for sunxvr500 driver

David S. Miller (3):
Merge branch 'master' of master.kernel.org:/.../davem/sparc-2.6
sparc64: If 'slot-names' property exist, create sysfs PCI slot information.
sparc: Support show_unhandled_signals.

FUJITA Tomonori (1):
sparc: use asm-generic/scatterlist.h

Frans Pop (1):
sparc: remove trailing space in messages

Jan Engelhardt (1):
sparc: remove redundant return statements

arch/sparc/include/asm/scatterlist.h | 21 +------
arch/sparc/kernel/devices.c | 2 -
arch/sparc/kernel/leon_kernel.c | 2 +-
arch/sparc/kernel/leon_smp.c | 4 +-
arch/sparc/kernel/pci.c | 75 ++++++++++++++++++++++++
arch/sparc/kernel/pcic.c | 2 -
arch/sparc/kernel/setup_32.c | 2 -
arch/sparc/kernel/sun4d_smp.c | 2 +-
arch/sparc/kernel/unaligned_64.c | 11 +---
arch/sparc/mm/fault_32.c | 106 +++++++++++++++++++---------------
arch/sparc/mm/fault_64.c | 34 ++++++++++-
arch/sparc/prom/console_32.c | 1 -
arch/sparc/prom/console_64.c | 1 -
arch/sparc/prom/devmap.c | 1 -
arch/sparc/prom/devops_32.c | 2 -
arch/sparc/prom/init_32.c | 1 -
arch/sparc/prom/palloc.c | 1 -
arch/sparc/prom/ranges.c | 2 -
arch/sparc/prom/segment.c | 1 -
arch/sparc/prom/tree_32.c | 1 -
arch/sparc/prom/tree_64.c | 1 -
drivers/video/sunxvr500.c | 1 +
kernel/sysctl.c | 2 +-
23 files changed, 176 insertions(+), 100 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

==============================================================================
TOPIC: i2c updates for 2.6.34, round 1
http://groups.google.com/group/linux.kernel/t/7b7f85629f7a9634?hl=en
==============================================================================

== 1 of 1 ==
Date: Tues, Mar 2 2010 4:50 am
From: Jean Delvare

Hi Linus,

Please pull a first round of i2c subsystem updates for Linux 2.6.34
from:

git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging.git i2c-for-linus

The main change here is the added support for the SMBus alert
protocols. And then come the usual random driver cleanups.

---------------

Jean Delvare (7):
i2c-tiny-usb: Fix a comment on bus frequency
i2c-parport: Give powered devices some time to settle
i2c: Add SMBus alert support
i2c: Separate Kconfig option for i2c-smbus
i2c-parport: Add SMBus alert support
i2c-parport-light: Add SMBus alert support
i2c-algo-pca: Drop duplicate variable

Mark Brown (1):
i2c: Hook up runtime PM support

Márton Németh (1):
i2c: Make PCI device ids constant

Seth Heasley (1):
i2c-i801: Add Intel Cougar Point device IDs

Zhangfei Gao (1):
i2c: Document the message size limit

Thanks,
--
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

==============================================================================
TOPIC: [4/4] SLAB: Fix node add timer race in cache_reap
http://groups.google.com/group/linux.kernel/t/a8beda1232363b5e?hl=en
==============================================================================

== 1 of 2 ==
Date: Tues, Mar 2 2010 5:00 am
From: Andi Kleen

> The first set of patches from Andi are almost one month old. If this issue
> progresses as swiftly as it has to this day, I foresee a rocky road for any

Yes it seems to be a bike shedding area for some reason (which color
should we paint it today?)

> of them getting merged to .34 through slab.git, that's all.

IMHO they are all bug fixes and there is no excuse for not merging them ASAP,
independent of any merge windows.

-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

== 2 of 2 ==
Date: Tues, Mar 2 2010 5:00 am
From: Andi Kleen

On Mon, Mar 01, 2010 at 02:24:43AM -0800, David Rientjes wrote:
> Slab lacks any memory hotplug support for nodes that are hotplugged
> without cpus being hotplugged. This is possible at least on x86
> CONFIG_MEMORY_HOTPLUG_SPARSE kernels where SRAT entries are marked
> ACPI_SRAT_MEM_HOT_PLUGGABLE and the regions of RAM represent a seperate
> node. It can also be done manually by writing the start address to
> /sys/devices/system/memory/probe for kernels that have
> CONFIG_ARCH_MEMORY_PROBE set, which is how this patch was tested, and
> then onlining the new memory region.

The patch looks far more complicated than my simple fix.

Is more complicated now better?

-Andi

--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

==============================================================================
TOPIC: usbaudio: Fix wrong bitrate for Creative Creative VF0470 Live Cam
http://groups.google.com/group/linux.kernel/t/829b9e9d076b418c?hl=en
==============================================================================

== 1 of 1 ==
Date: Tues, Mar 2 2010 5:00 am
From: Arseniy Lartsev

This patch works around misbehaviour of Creative Creative VF0470 Live Cam
which reports 16 kHz sample rate for audio capture while actually producing
8 kHz stream.

Signed-off-by: Arseniy Lartsev <arseniy@fizlesh.ru>

--
diff -rup linux-2.6.33-rc8-orig/sound/usb/usbaudio.c linux-2.6.33-
rc8/sound/usb/usbaudio.c
--- linux-2.6.33-rc8-orig/sound/usb/usbaudio.c
+++ linux-2.6.33-rc8/sound/usb/usbaudio.c
@@ -2513,6 +2513,9 @@ static int parse_audio_format_rates(stru
chip->usb_id == USB_ID(0x0d8c, 0x0102)) &&
fp->altsetting == 5 && fp->maxpacksize == 392)
rate = 96000;
+ /* Creative VF0470 Live Cam reports 16 kHz instead of 8 */
+ if ((rate == 16000) && (chip->usb_id == USB_ID(0x041e, 0x4068)))
+ rate = 8000;
fp->rate_table[fp->nr_rates] = rate;
if (!fp->rate_min || rate < fp->rate_min)
fp->rate_min = rate;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

==============================================================================
TOPIC: memcg: dirty pages accounting and limiting infrastructure
http://groups.google.com/group/linux.kernel/t/98b8f3d66410be44?hl=en
==============================================================================

== 1 of 5 ==
Date: Tues, Mar 2 2010 5:10 am
From: Balbir Singh

* Andrea Righi <arighi@develer.com> [2010-03-01 22:23:39]:

> Infrastructure to account dirty pages per cgroup and add dirty limit
> interfaces in the cgroupfs:
>
> - Direct write-out: memory.dirty_ratio, memory.dirty_bytes
>
> - Background write-out: memory.dirty_background_ratio, memory.dirty_background_bytes
>
> Signed-off-by: Andrea Righi <arighi@develer.com>

Look good, but yet to be tested from my side.

> ---
> include/linux/memcontrol.h | 77 ++++++++++-
> mm/memcontrol.c | 336 ++++++++++++++++++++++++++++++++++++++++----
> 2 files changed, 384 insertions(+), 29 deletions(-)
>
> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> index 1f9b119..cc88b2e 100644
> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -19,12 +19,50 @@
>
> #ifndef _LINUX_MEMCONTROL_H
> #define _LINUX_MEMCONTROL_H
> +
> +#include <linux/writeback.h>
> #include <linux/cgroup.h>
> +
> struct mem_cgroup;
> struct page_cgroup;
> struct page;
> struct mm_struct;
>
> +/* Cgroup memory statistics items exported to the kernel */
> +enum mem_cgroup_page_stat_item {
> + MEMCG_NR_DIRTYABLE_PAGES,
> + MEMCG_NR_RECLAIM_PAGES,
> + MEMCG_NR_WRITEBACK,
> + MEMCG_NR_DIRTY_WRITEBACK_PAGES,
> +};
> +
> +/*
> + * Statistics for memory cgroup.
> + */
> +enum mem_cgroup_stat_index {
> + /*
> + * For MEM_CONTAINER_TYPE_ALL, usage = pagecache + rss.
> + */
> + MEM_CGROUP_STAT_CACHE, /* # of pages charged as cache */
> + MEM_CGROUP_STAT_RSS, /* # of pages charged as anon rss */
> + MEM_CGROUP_STAT_FILE_MAPPED, /* # of pages charged as file rss */
> + MEM_CGROUP_STAT_PGPGIN_COUNT, /* # of pages paged in */
> + MEM_CGROUP_STAT_PGPGOUT_COUNT, /* # of pages paged out */
> + MEM_CGROUP_STAT_EVENTS, /* sum of pagein + pageout for internal use */
> + MEM_CGROUP_STAT_SWAPOUT, /* # of pages, swapped out */
> + MEM_CGROUP_STAT_SOFTLIMIT, /* decrements on each page in/out.
> + used by soft limit implementation */
> + MEM_CGROUP_STAT_THRESHOLDS, /* decrements on each page in/out.
> + used by threshold implementation */
> + MEM_CGROUP_STAT_FILE_DIRTY, /* # of dirty pages in page cache */
> + MEM_CGROUP_STAT_WRITEBACK, /* # of pages under writeback */
> + MEM_CGROUP_STAT_WRITEBACK_TEMP, /* # of pages under writeback using
> + temporary buffers */
> + MEM_CGROUP_STAT_UNSTABLE_NFS, /* # of NFS unstable pages */
> +
> + MEM_CGROUP_STAT_NSTATS,
> +};
> +
> #ifdef CONFIG_CGROUP_MEM_RES_CTLR
> /*
> * All "charge" functions with gfp_mask should use GFP_KERNEL or
> @@ -117,6 +155,13 @@ extern void mem_cgroup_print_oom_info(struct mem_cgroup *memcg,
> extern int do_swap_account;
>

twitter

Tuesday, March 2, 2010

linux.kernel - 26 new messages in 17 topics - digest

0 Comments:

Post a Comment

About Me

Previous Posts