On 2018/12/28 上午10:55, Waiman Long wrote:
> On 12/27/2018 08:31 PM, Wang, Kemi wrote:
>> Hi, Waiman
>>Did you post that patch? Let's see if it helps.
>
> I did post the patch a while ago. I will need to rebase it to a new
> baseline. Will do that in a week or
Hi, Waiman
Did you post that patch? Let's see if it helps.
-Original Message-
From: LKP [mailto:lkp-boun...@lists.01.org] On Behalf Of Waiman Long
Sent: Tuesday, November 6, 2018 6:40 AM
To: Linus Torvalds ; vba...@suse.cz; Davidlohr
Bueso
Cc: yang@linux.alibaba.com; Linux Kernel
Hi, All
Do we have special reason to keep this patch (316ba5736c9:brd: Mark as
non-rotational).
which leads to a performance regression when BRD is used as a disk on btrfs.
On 2018/7/10 下午1:27, kemi wrote:
> Hi, SeongJae
> Do you have any input for this regression? thanks
>
> On
Hi, SeongJae
Any update or any info you need from my side?
-Original Message-
From: SeongJae Park [mailto:sj38.p...@gmail.com]
Sent: Wednesday, July 11, 2018 12:53 AM
To: Wang, Kemi
Cc: Ye, Xiaolong ; ax...@kernel.dk; ax...@fb.com;
l...@01.org; linux-kernel@vger.kernel.org
Subject: Re
Hi, SeongJae
Do you have any input for this regression? thanks
On 2018年06月04日 13:52, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -11.2% regression of aim7.jobs-per-min due to commit:
>
>
> commit: 316ba5736c9caa5dbcd84085989862d2df57431d ("brd: Mark as
> non-rotational")
>
;
pau...@samba.org; Thomas Gleixner ; Ingo Molnar
; h...@zytor.com; Will Deacon ; Sergey
Senozhatsky ; sergey.senozhatsky.w...@gmail.com;
Andrea Arcangeli ; Alexei Starovoitov
; Wang, Kemi ; Daniel Jordan
; David Rientjes ; Jerome
Glisse ; Ganesh Mahendran ;
Minchan Kim ; Punit Agrawal
Hi, Jeff
Today, I deleted the previous kernel images for commit
3da90b159b146672f830bcd2489dd3a1f4e9e089
and commit c0cef30e4ff0dc025f4a1660b8f0ba43ed58426e, respectively. And, re-run
the same aim7
jobs for three times for each commit. The aim7 score between two commit does
not have obvious
On 2018年02月28日 01:04, Linus Torvalds wrote:
> On Tue, Feb 27, 2018 at 5:43 AM, David Howells wrote:
>> Is it possible there's a stall between the load of RCX and the subsequent
>> instructions because they all have to wait for RCX to become available?
>
> No. Modern Intel big-core CPU's simply
On 2018年02月26日 20:33, Jeff Layton wrote:
> On Mon, 2018-02-26 at 06:43 -0500, Jeff Layton wrote:
>> On Mon, 2018-02-26 at 16:38 +0800, Ye Xiaolong wrote:
>>> On 02/25, Jeff Layton wrote:
On Sun, 2018-02-25 at 23:05 +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a
Hi, Jens
Could you help to merge this patch to your tree? Thanks
On 2017年11月03日 10:29, kemi wrote:
>
>
> On 2017年10月24日 09:16, Kemi Wang wrote:
>> It's expensive to set buffer flags that are already set, because that
>> causes a costly cache line transition.
>>
On 2017年12月22日 01:10, Christopher Lameter wrote:
> On Thu, 21 Dec 2017, kemi wrote:
>
>> Some thinking about that:
>> a) the overhead due to cache bouncing caused by NUMA counter update in fast
>> path
>> severely increase with more and more CPUs cores
>>
On 2017年12月21日 16:59, Michal Hocko wrote:
> On Thu 21-12-17 16:23:23, kemi wrote:
>>
>>
>> On 2017年12月21日 16:17, Michal Hocko wrote:
> [...]
>>> Can you see any difference with a more generic workload?
>>>
>>
>> I didn't see obvious i
On 2017年12月21日 16:17, Michal Hocko wrote:
> On Thu 21-12-17 16:06:50, kemi wrote:
>>
>>
>> On 2017年12月20日 18:12, Michal Hocko wrote:
>>> On Wed 20-12-17 13:52:14, kemi wrote:
>>>>
>>>>
>>>> On 2017年12月19日 20:40, Michal Hocko wrot
On 2017年12月20日 18:12, Michal Hocko wrote:
> On Wed 20-12-17 13:52:14, kemi wrote:
>>
>>
>> On 2017年12月19日 20:40, Michal Hocko wrote:
>>> On Tue 19-12-17 14:39:24, Kemi Wang wrote:
>>>> We have seen significant overhead in cache bouncing caused by NUMA c
On 2017年12月20日 23:58, Christopher Lameter wrote:
> On Wed, 20 Dec 2017, kemi wrote:
>
>>> You are making numastats special and I yet haven't heard any sounds
>>> arguments for that. But that should be discussed in the respective
>>> patch.
>>>
>
On 2017年12月20日 18:06, Michal Hocko wrote:
> On Wed 20-12-17 14:07:35, kemi wrote:
>>
>>
>> On 2017年12月19日 20:43, Michal Hocko wrote:
>>> On Tue 19-12-17 14:39:25, Kemi Wang wrote:
>>>> To avoid deviation, this patch uses node_page_state_snapshot ins
On 2017年12月20日 18:12, Michal Hocko wrote:
> On Wed 20-12-17 13:52:14, kemi wrote:
>>
>>
>> On 2017年12月19日 20:40, Michal Hocko wrote:
>>> On Tue 19-12-17 14:39:24, Kemi Wang wrote:
>>>> We have seen significant overhead in cache bouncing caused by NUMA c
On 2017年12月20日 01:21, Christopher Lameter wrote:
> On Tue, 19 Dec 2017, Michal Hocko wrote:
>
>>> Well the reason for s8 was to keep the data structures small so that they
>>> fit in the higher level cpu caches. The large these structures become the
>>> more cachelines are used by the counters a
On 2017年12月19日 20:43, Michal Hocko wrote:
> On Tue 19-12-17 14:39:25, Kemi Wang wrote:
>> To avoid deviation, this patch uses node_page_state_snapshot instead of
>> node_page_state for node page stats query.
>> e.g. cat /proc/zoneinfo
>> cat /sys/devices/system/no
On 2017年12月19日 20:40, Michal Hocko wrote:
> On Tue 19-12-17 14:39:24, Kemi Wang wrote:
>> We have seen significant overhead in cache bouncing caused by NUMA counters
>> update in multi-threaded page allocation. See 'commit 1d90ca897cb0 ("mm:
>> update NUMA cou
On 2017年12月19日 20:28, Michal Hocko wrote:
> On Tue 19-12-17 14:39:22, Kemi Wang wrote:
>> There is not really any use to get NUMA stats separated by zone, and
>> current per-zone NUMA stats is only consumed in /proc/zoneinfo. For code
>> cleanup purpose, we move NUMA stats
On 2017年12月19日 20:38, Michal Hocko wrote:
> On Tue 19-12-17 14:39:23, Kemi Wang wrote:
>> The type s8 used for vm_diff_nodestat[] as local cpu counters has the
>> limitation of global counters update frequency, especially for those
>> monotone increasing type of counters li
Hocko
Signed-off-by: Kemi Wang
---
drivers/base/node.c| 23 +++
include/linux/mmzone.h | 27
include/linux/vmstat.h | 31 -
mm/mempolicy.c | 2 +-
mm/page_alloc.c| 16 +++--
mm/vmstat.c| 177
Since the functionality of zone_statistics() updates numa counters, but
numa statistics has been separated from zone statistics framework. Thus,
the function name makes people confused. So, change the name to
numa_statistics() as well as its call sites accordingly.
Signed-off-by: Kemi Wang
worry about
it.
Signed-off-by: Kemi Wang
---
drivers/base/node.c | 17 ++---
mm/vmstat.c | 2 +-
2 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/drivers/base/node.c b/drivers/base/node.c
index a045ea1..cf303f8 100644
--- a/drivers/base/node.c
+++ b/drivers
any functionality change.
before after
sizeof(struct per_cpu_nodestat)28 68
Signed-off-by: Kemi Wang
---
include/linux/mmzone.h | 4 ++--
mm/vmstat.c| 16
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git
nd deals
with global counter update using different threshold size for node page
stats.
Signed-off-by: Kemi Wang
---
mm/vmstat.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/mm/vmstat.c b/mm/vmstat.c
index 9c681cc..64e08ae 100644
--- a/mm/vmstat.c
+++ b/mm/vms
per-cpu infrastructure for node page stats by
entending local cpu counters vm_node_stat_diff from s8 to s16
b) reuse the per-cpu infrastrcuture for NUMA stats
Kemi Wang (5):
mm: migrate NUMA stats from per-zone to per-node
mm: Extends local cpu counter vm_diff_nodestat from s8 to s16
On 2017年12月14日 15:29, Michal Hocko wrote:
> On Thu 14-12-17 09:40:32, kemi wrote:
>>
>>
>> or sometimes
>> NUMA stats can't be disabled in their environments.
>
> why?
>
>> That's the reason
>> why we spent time to do that optimi
On 2017年12月12日 16:11, Michal Hocko wrote:
> On Tue 12-12-17 10:05:26, kemi wrote:
>>
>>
>> On 2017年12月08日 16:47, Michal Hocko wrote:
>>> On Fri 08-12-17 16:38:46, kemi wrote:
>>>>
>>>>
>>>> On 2017年11月30日 17:45, Michal Hocko
On 2017年12月08日 16:47, Michal Hocko wrote:
> On Fri 08-12-17 16:38:46, kemi wrote:
>>
>>
>> On 2017年11月30日 17:45, Michal Hocko wrote:
>>> On Thu 30-11-17 17:32:08, kemi wrote:
>>
>> After thinking about how to optimize our per-node stats more gracefully,
On 2017年11月30日 17:45, Michal Hocko wrote:
> On Thu 30-11-17 17:32:08, kemi wrote:
> Do not get me wrong. If we want to make per-node stats more optimal,
> then by all means let's do that. But having 3 sets of counters is just
> way to much.
>
Hi, Michal
Apologize to r
Of course, we should do that AFAP. Thanks for your comments :)
-Original Message-
From: owner-linux...@kvack.org [mailto:owner-linux...@kvack.org] On Behalf Of
Michal Hocko
Sent: Thursday, November 30, 2017 5:45 PM
To: Wang, Kemi
Cc: Greg Kroah-Hartman ; Andrew Morton
; Vlastimil Babka
On 2017年11月30日 16:53, Michal Hocko wrote:
> On Thu 30-11-17 13:56:13, kemi wrote:
>>
>>
>> On 2017年11月29日 20:17, Michal Hocko wrote:
>>> On Tue 28-11-17 14:00:23, Kemi Wang wrote:
>>>> The existed implementation of NUMA counters is per logical CPU alon
On 2017年11月29日 20:17, Michal Hocko wrote:
> On Tue 28-11-17 14:00:23, Kemi Wang wrote:
>> The existed implementation of NUMA counters is per logical CPU along with
>> zone->vm_numa_stat[] separated by zone, plus a global numa counter array
>> vm_numa_stat[]. However,
On 2017年11月28日 16:09, Vlastimil Babka wrote:
> On 11/28/2017 07:00 AM, Kemi Wang wrote:
>> The existed implementation of NUMA counters is per logical CPU along with
>> zone->vm_numa_stat[] separated by zone, plus a global numa counter array
>> vm_numa_stat[]. However,
Since numa statistics has been separated from zone statistics framework,
but the functionality of zone_statistics() updates numa counters. Thus, the
function name makes people confused. So, change the name to
numa_statistics() as well as its call sites accordingly.
Signed-off-by: Kemi Wang
ices/system/sys 0m0.001s sys 0m0.000s
node/node*/numastat
We would not worry it much as it is a slow path and will not be read
frequently.
Suggested-by: Andi Kleen
Signed-off-by: Kemi Wang
---
drivers/base/node.c| 14 ++---
include/linux/mmzone.h | 2 -
include/linux/v
Some performance regression/improvement is reported by LKP-tools for this patch
series
tested with Intel Atom processor. So, post the data here for your reference.
Branch:x86/entry_consolidation
Commit id:
base:50da9d439392fdd91601d36e7f05728265bff262
head:69af865668fdb86a95e4e948b1f48b
On 2017年11月08日 05:38, Kees Cook wrote:
> The mutex in sysctl_vm_numa_stat_handler() needs to be a global static, not
> a stack variable, otherwise it doesn't serve any purpose. Also, reading the
> file with CONFIG_LOCKDEP=y will complain:
>
It's my mistake. Kees, thanks for catching it.
> [
On 2017年10月24日 09:16, Kemi Wang wrote:
> It's expensive to set buffer flags that are already set, because that
> causes a costly cache line transition.
>
> A common case is setting the "verified" flag during ext4 writes.
> This patch checks for the flag being set f
Some regression is found by LKP-tools(linux kernel performance) on this patch
series
tested on Intel 2s/4s Skylake platform.
The regression result is sorted by the metric will-it-scale.per_process_ops.
Branch:Laurent-Dufour/Speculative-page-faults/20171011-213456(V4 patch series)
Commit id:
On 2017年10月24日 09:21, Andi Kleen wrote:
> kemi writes:
>>
>> I'll see if I can find some
>>> time to implement the above in a nice way.
>>
>> Agree. Maybe something like test_and_set_bit() would be more suitable.
>
> test_and_set_bit is a very
The original patch is contributed by Andi Kleen.
Signed-off-by: Andi Kleen
Signed-off-by: Kemi Wang
Tested-by: Kemi Wang
Reviewed-by: Jens Axboe
---
include/linux/buffer_head.h | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/buffer_head.h b/include/linux/b
On 2017年10月24日 00:19, Jens Axboe wrote:
> On 10/23/2017 10:27 AM, Kemi Wang wrote:
>> It's expensive to set buffer flags that are already set, because that
>> causes a costly cache line transition.
>>
>> A common case is setting the "verified" flag du
The original patch is contributed by Andi Kleen.
Signed-off-by: Andi Kleen
Signed-off-by: Kemi Wang
Tested-by: Kemi Wang
---
include/linux/buffer_head.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/buffer_head.h b/include/linux/buffer_head.h
index c8dae
ported-by: Jesper Dangaard Brouer
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
Signed-off-by: Kemi Wang
---
Documentation/sysctl/vm.txt | 16 +++
include/linux/vmstat.h | 10 +++
kernel/sysctl.c | 9 ++
mm/mempolicy.c | 3 ++
mm/pag
On 2017年10月17日 15:54, Michal Hocko wrote:
> On Tue 17-10-17 09:20:58, Kemi Wang wrote:
> [...]
>
> Other than two remarks below, it looks good to me and it also looks
> simpler.
>
>> diff --git a/mm/vmstat.c b/mm/vmstat.c
>> index 4bb13e7..e746ed1 100644
&g
ned.
Reported-by: Jesper Dangaard Brouer
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
Signed-off-by: Kemi Wang
---
Documentation/sysctl/vm.txt | 16 +++
include/linux/vmstat.h | 10 +++
kernel/sysctl.c | 7 +
mm/mempolicy.c | 3 ++
mm/page_a
On 2017年10月10日 13:49, Michal Hocko wrote:
> On Mon 09-10-17 09:55:49, Michal Hocko wrote:
>> I haven't checked closely but what happens (or should happen) when you
>> do a partial read? Should you get an inconsistent results? Or is this
>> impossible?
>
> Well, after thinking about it little bit
On 2017年10月03日 17:23, Michal Hocko wrote:
> On Thu 28-09-17 14:11:41, Kemi Wang wrote:
>> This is the second step which introduces a tunable interface that allow
>> numa stats configurable for optimizing zone_statistics(), as suggested by
>> Dave
On 2017年09月29日 15:03, Vlastimil Babka wrote:
> On 09/28/2017 08:11 AM, Kemi Wang wrote:
>> This is the second step which introduces a tunable interface that allow
>> numa stats configurable for optimizing zone_statistics(), as suggested by
>> Dave
On 2017年09月29日 05:29, Andrew Morton wrote:
> On Thu, 28 Sep 2017 14:11:41 +0800 Kemi Wang wrote:
>
>> This is the second step which introduces a tunable interface that allow
>> numa stats configurable for optimizing zone_statistics(), as suggested by
>> Dave Hansen an
sper Dangaard Brouer
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
Signed-off-by: Kemi Wang
---
Documentation/sysctl/vm.txt | 24 +
drivers/base/node.c | 4 ++
include/linux/vmstat.h | 23
init/main.c | 3 ++
kernel/sysctl.c
On 2017年09月25日 09:36, Huang, Ying wrote:
> Kemi Wang writes:
>
>> This is the second step which introduces a tunable interface that allow VM
>> stats configurable for optimizing zone_statistics(), as suggested by Dave
>&g
jump label to eliminate the overhead of branch selection;
c) Add a single-time log message at boot time to help tell users what
happened.
Reported-by: Jesper Dangaard Brouer
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
Signed-off-by: Kemi Wang
---
Documentation/sysctl/vm.txt | 26 ++
On 2017年09月18日 12:13, Dave Hansen wrote:
> On 09/17/2017 08:07 PM, kemi wrote:
>>>> + if (vmstat_mode) {
>>>> + if (vmstat_mode == VMSTAT_COARSE_MODE)
>>>> + return;
>>>> + } else if (disable_zone_statistics)
On 2017年09月15日 19:49, Michal Hocko wrote:
> On Fri 15-09-17 17:23:24, Kemi Wang wrote:
>> This patch adds a tunable interface that allows VM stats configurable, as
>> suggested by Dave Hansen and Ying Huang.
>>
>> When performance becomes a bottleneck and you can tol
On 2017年09月15日 19:50, Michal Hocko wrote:
> On Fri 15-09-17 17:23:25, Kemi Wang wrote:
> [...]
>> @@ -2743,6 +2745,17 @@ static inline void zone_statistics(struct zone
>> *preferred_zone, struct zone *z)
>> #ifdef CONFIG_NUMA
>> enum numa_sta
On 2017年09月15日 22:28, Michal Hocko wrote:
> On Fri 15-09-17 07:16:23, Dave Hansen wrote:
>> On 09/15/2017 04:49 AM, Michal Hocko wrote:
>>> Why do we need an auto-mode? Is it safe to enforce by default.
>>
>> Do we *need* it? Not really.
>>
>> But, it does offer the best of both worlds: The vast
-Original Message-
From: Michal Hocko [mailto:mho...@kernel.org]
Sent: Friday, September 15, 2017 7:50 PM
To: Wang, Kemi
Cc: Luis R . Rodriguez ; Kees Cook ;
Andrew Morton ; Jonathan Corbet ;
Mel Gorman ; Johannes Weiner ;
Christopher Lameter ; Sebastian Andrzej Siewior
; Vlastimil
tps://github.com/netoptimizer/prototype-kernel/tree/master/kernel/mm/
bench
Reported-by: Jesper Dangaard Brouer
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
Signed-off-by: Kemi Wang
---
drivers/base/node.c| 2 ++
include/linux/vmstat.h | 6 +
mm/page_alloc.c| 13
can do:
echo [A|a]uto > /proc/sys/vm/vmstat_mode
The next patch handles numa statistics distinctively based-on different VM
stats mode.
Reported-by: Jesper Dangaard Brouer
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
Signed-off-by: Kemi Wang
---
include/linux/vmstat.h | 14 +
Add a paragraph to introduce the functionality and usage on vmstat_mode in
sysctl/vm.txt
Reported-by: Jesper Dangaard Brouer
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
Signed-off-by: Kemi Wang
---
Documentation/sysctl/vm.txt | 26 ++
1 file changed, 26
ds for single page allocation.
The third patch updates ABI document accordingly.
Kemi Wang (3):
mm, sysctl: make VM stats configurable
mm: Handle numa statistics distinctively based-on different VM stats
modes
sysctl/vm.txt: Update document
Documentation/sysctl/vm.txt
he consistant numa threshold.
d) Move zone_numa_state_snapshot() to an individual patch, since it
does not appear to be related to this patch.
Signed-off-by: Kemi Wang
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
---
include/linux/mmzone.h | 3 +--
mm/vmstat.c| 28
000 394 489009617
3 395 488017817
65533 369(-31.3%) 521661345(+45.3%) <==> with this patchset
N/A 342(-36.3%) 562900157(+56.8%) <==> disable zone_statistics
Kemi Wang (3):
mm: Change the call sites of numa statistics items
mm: Update N
.
Changelog:
v2:
a) Modify the name of numa-stats-specific functions and params to avoid
confusion with those for zone/node page stats.
b) Get rid of showing the number of numa stat threshold in /proc/zoneinfo
since the value of this item is a constant.
Signed-off-by: Kemi Wang
---
drivers/base/node.c
.
Changelog:
v2:
a) new creation.
Signed-off-by: Kemi Wang
---
include/linux/vmstat.h | 6 +-
mm/vmstat.c| 9 +++--
2 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/include/linux/vmstat.h b/include/linux/vmstat.h
index a29bd98..72e9ca6 100644
--- a/include/linux
On 2017年08月23日 05:22, Christopher Lameter wrote:
> Can we simple get rid of the stats or make then configurable (off by
> defaut)? I agree they are rarely used and have been rarely used in the past.
>
I agree that we can make numa stats as well as other stats items that are rarely
used configur
On 2017年08月15日 17:58, Mel Gorman wrote:
> On Tue, Aug 15, 2017 at 04:45:36PM +0800, Kemi Wang wrote:
>> Threshold CPU cyclesThroughput(88 threads)
>> 32 799 241760478
>> 64 640 301628829
>> 125 537
On 2017年08月15日 18:36, Jesper Dangaard Brouer wrote:
> On Tue, 15 Aug 2017 16:45:34 +0800
> Kemi Wang wrote:
>
>> Each page allocation updates a set of per-zone statistics with a call to
>> zone_statistics(). As discussed in 2017 MM submit, th
On 2017年08月16日 00:55, Tim Chen wrote:
> On 08/15/2017 02:58 AM, Mel Gorman wrote:
>> On Tue, Aug 15, 2017 at 04:45:36PM +0800, Kemi Wang wrote:
>> I'm fairly sure this pushes the size of that structure into the next
>> cache line which is not welcome.
>>&
>>
>> -static inline unsigned long zone_numa_state(struct zone *zone,
>> +static inline unsigned long zone_numa_state_snapshot(struct zone *zone,
>> enum zone_numa_stat_item item)
>> {
>> long x = atomic_long_read(&zone->vm_numa_stat[item]);
>> +int
On 2017年08月15日 17:49, Mel Gorman wrote:
> On Tue, Aug 15, 2017 at 04:45:35PM +0800, Kemi Wang wrote:
>> In this patch, NUMA statistics is separated from zone statistics
>> framework, all the call sites of NUMA stats are changed to use
>> numa-stats-specific functions,
threshold: 10*
...
The next patch updates the numa stats counter size and threshold.
Signed-off-by: Kemi Wang
---
drivers/base/node.c| 22 ---
include/linux/mmzone.h | 25 +---
include/linux/vmstat.h | 29 +
mm/page_alloc.c
489009617
3 395 488017817
32765 394(-26.6%) 488932078(+36.2%) <==> with this patchset
N/A 342(-36.3%) 562900157(+56.8%) <==> disable zone_statistics
Kemi Wang (2):
mm: Change the call sites of numa statistics items
mm: Update NUMA counter t
2%) <==> with this patchset
N/A 342(-36.3%) 562900157(+56.8%) <==> disable zone_statistics
Signed-off-by: Kemi Wang
Suggested-by: Dave Hansen
Suggested-by: Ying Huang
---
include/linux/mmzone.h | 4 ++--
include/linux/vmstat.h | 6 +-
mm/vmstat.c| 23 +
Hi all.
Ok, maybe this isn't the right list for this question. In 2.2.x the
parport_probe module extracted the ieee1284 device id correctly and added to the
proc fs. However this doesn't seem to work for me in 2.4.x
I only have one device to test it on and since I know there have been some
diffic
Hi all.
Ok, maybe this isn't the right list for this question. In 2.2.x the
parport_probe module extracted the ieee1284 device id correctly and added to the
proc fs. However this doesn't seem to work for me in 2.4.x
I only have one device to test it on and since I know there have been some
diffic
The w9966cf webcam v4l driver now has a homepage:
http://hem.fyristorg.com/mogul/w9966.html
-
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 F
2/Documentation/video4linux/w9966.txt Tue Mar 27 01:02:00 2001
@@ -0,0 +1,37 @@
+
+W9966 Camera driver, written by Jakob Kemi ([EMAIL PROTECTED])
+
+Ok, after a lot of work in softice, wdasm, reading pdf-files
+and trial-and-error work I've finally got everything to work.
+Since I neede
-X dontdiff linux-vanilla/Documentation/video4linux/w9966.txt
linux-2.4.2/Documentation/video4linux/w9966.txt
--- linux-vanilla/Documentation/video4linux/w9966.txt Thu Jan 1 01:00:00 1970
+++ linux-2.4.2/Documentation/video4linux/w9966.txt Tue Mar 27 01:02:00 2001
@@ -0,0 +1,37 @@
+
+W9966 Camera driv
83 matches
Mail list logo
