[EMAIL PROTECTED] wrote:
> On Mon, 15 Oct 2007, Stefan Richter wrote:
>> Low-level networking drivers suggest a default interface name (per
>> interface or as a template like eth%d into which the networking core
>> inserts a lowest spare number).
...
>> Could low-level SCSI drivers provide similar
On 10/16/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> On 10/15/07, Bryan Wu <[EMAIL PROTECTED]> wrote:
> > On 10/15/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> > >
> > > Completion is just not a good abstraction here... Please use work
> > > abstraction and possibly a separate workqueue.
On Mon, Oct 15, 2007 at 01:50:42PM +0200, Bernhard Walle wrote:
> I observed the problem that even when you choose the default 16M as
> crashkernel base address and the kernel is very big, the reserved area may
> overlap with the kernel BSS. Currently, this is not checked at runtime, so the
>
Hi,
The build fails with following error
CC drivers/usb/storage/scsiglue.o
CC drivers/usb/storage/protocol.o
CC drivers/usb/storage/transport.o
In file included from drivers/usb/storage/transport.c:53:
include/scsi/scsi_eh.h:79: error: field 'sense_sgl' has incomplete type
Ingo Molnar wrote:
* Jeff Garzik <[EMAIL PROTECTED]> wrote:
Two comments:
1) we have a vague definition of "RX work processed." Due to error
conditions and goto's in that function, rx_processed_cnt may or may
not equal the number of packets actually processed.
2) man I dislike these
On 10/14/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> I didn't notice that qemu was involved. Does qemu have an emulator for the
> gdth hardware?
>
I think no, the kernel just probe exist or not hardware, and hangs after that.
-
To unsubscribe from this list: send the line "unsubscribe
* Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Two comments:
>
> 1) we have a vague definition of "RX work processed." Due to error
> conditions and goto's in that function, rx_processed_cnt may or may
> not equal the number of packets actually processed.
>
> 2) man I dislike these inline C
On Mon, Oct 15, 2007 at 10:37:04AM -0700, Yinghai Lu wrote:
> Greg,
>
> from linus's git this morning..
>
> ACPI: PCI Interrupt :00:02.1[B] -> Link [LUB2] -> GSI 21 (level,
> low) -> IRQ 21
> ehci_hcd :00:02.1: EHCI Host Controller
> ehci_hcd :00:02.1: new USB bus registered,
On Tuesday 16 October 2007 14:57, Eric W. Biederman wrote:
> Nick Piggin <[EMAIL PROTECTED]> writes:
> >> make_page_uptodate() is most hideous part I have run into.
> >> It has to know details about other layers to now what not
> >> to stomp. I think my incorrect simplification of this is what
Hi,
While running kernbench with the 2.6.23-git8 following oops is produced
Unable to handle kernel NULL pointer dereference at 0010 RIP:
[] __rb_rotate_left+0x7/0x70
PGD 31f7ad067 PUD 31f14d067 PMD 0
Oops: [1] SMP
CPU 8
Modules linked in: loop dm_mod md_mod sg
Pid: 6923,
On Mon, 15 Oct 2007, Matt Mackall wrote:
> Index: l/init/Kconfig
> ===
> --- l.orig/init/Kconfig 2007-10-14 13:35:07.0 -0500
> +++ l/init/Kconfig2007-10-15 17:18:16.0 -0500
> @@ -571,6 +571,15 @@ config SLOB
>On 10/16/07, Greg KH <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 15, 2007 at 02:38:25PM -0400, Alan Stern wrote:
> > On Mon, 15 Oct 2007, Dave Young wrote:
> >
> > > On 10/14/07, Borislav Petkov <[EMAIL PROTECTED]> wrote:
> > > > Hi,
> > > >
> > > > i get the following warning on yesterday's git
> Will do - I justed wanted to get this quickly out to show the idea
> that I was working on.
Ok - good.
In the final analysis, I'll take whatever works ;).
I'll lobby for keeping the code "simple" (a subjective metric) and poke
what holes I can in things, and propose what alternatives I can
On Mon, 15 Oct 2007, Matt Mackall wrote:
> Index: l/fs/proc/task_mmu.c
> ===
> --- l.orig/fs/proc/task_mmu.c 2007-10-14 13:38:43.0 -0500
> +++ l/fs/proc/task_mmu.c 2007-10-14 13:39:00.0 -0500
> @@ -324,19 +324,47
On Monday 15 October 2007 11:29:58 pm Sam Ravnborg wrote:
> Hi Rob & Jan.
>
> On Fri, Oct 12, 2007 at 11:44:08PM +0200, Jan Engelhardt wrote:
> > Allow config variables in .config to override earlier ones in the same
> > file. In other words,
> >
> > # CONFIG_SECURITY is not defined
> >
On 10/15/07, Paul Jackson <[EMAIL PROTECTED]> wrote:
> > currently against an older kernel
>
> ah .. which older kernel?
2.6.18, but I can do a version against 2.6.23-mm1.
> + if (!retval) {
> + cpus_allowed = cpuset_cpus_allowed(p);
> + if
Jarek Poplawski wrote:
On 13-10-2007 03:29, Peter Williams wrote:
Jarek Poplawski wrote:
On 12-10-2007 00:23, Peter Williams wrote:
...
The reason I was going that route was for modularity (which helps
when adding plugsched patches). I'll submit a revised patch for
consideration.
...
On Mon, 15 Oct 2007, Matt Mackall wrote:
> Use the generic pagewalker for smaps and clear_refs
>
> Signed-off-by: Matt Mackall <[EMAIL PROTECTED]>
Acked-by: David Rientjes <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, 15 Oct 2007, Matt Mackall wrote:
> Introduce a general page table walker
>
> Signed-off-by: Matt Mackall <[EMAIL PROTECTED]>
>
> Index: l/include/linux/mm.h
> ===
> --- l.orig/include/linux/mm.h 2007-10-09
Nick Piggin <[EMAIL PROTECTED]> writes:
>>
>> make_page_uptodate() is most hideous part I have run into.
>> It has to know details about other layers to now what not
>> to stomp. I think my incorrect simplification of this is what messed
>> things up, last round.
>
> Not really, it's just named
On Mon, 15 Oct 2007, Greg KH wrote:
On Mon, Oct 15, 2007 at 10:04:01PM -0600, Matthew Wilcox wrote:
On Mon, Oct 15, 2007 at 07:54:22PM -0700, [EMAIL PROTECTED] wrote:
do PCI devices reorder their bus numbers spontaniously, or only if you
change the hardware?
The only system I've had that
On Sat, Oct 13, 2007 at 09:26:32PM +0200, Rafael J. Wysocki wrote:
> Hi,
>
> There are many traces like this in my dmesg from 2.6.23-git3 (they don't
> appear for vanilla 2.6.23):
>
> <4>sysfs: duplicate filename 'ethxx1' can not be created
> WARNING: at
On Tuesday 16 October 2007 14:38, Eric W. Biederman wrote:
> Nick Piggin <[EMAIL PROTECTED]> writes:
> > On Tuesday 16 October 2007 13:55, Eric W. Biederman wrote:
> > I don't follow your logic. We don't need SWAP > RAM in order to swap
> > effectively, IMO.
>
> The steady state of a system that
On Mon, Oct 15, 2007 at 02:38:25PM -0400, Alan Stern wrote:
> On Mon, 15 Oct 2007, Dave Young wrote:
>
> > On 10/14/07, Borislav Petkov <[EMAIL PROTECTED]> wrote:
> > > Hi,
> > >
> > > i get the following warning on yesterday's git tree
> > > (v2.6.23-2840-g752097c):
> > >
> > > Oct 14 09:07:15
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> > please pull the lockdep tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep.git
> > v2.6.24-lockdep
>
> Hmm. I'm now getting
>
> WARNING: at kernel/lockdep.c:700 look_up_lock_class()
it triggered
[EMAIL PROTECTED] writes:
>
> on some kernel versions you are correct about needing swap > ram, but on
> current
> versions you are not. the swap space gets allocated as needed, and re-used as
> needed (I don't know the mechanism of this, but I remember the last time this
> changed from
Nick Piggin <[EMAIL PROTECTED]> writes:
> On Tuesday 16 October 2007 13:55, Eric W. Biederman wrote:
>> Nick Piggin <[EMAIL PROTECTED]> writes:
>
>> > How much swap do you have configured? You really shouldn't configure
>> > so much unless you do want the kernel to actually use it all, right?
>>
Hi Rob & Jan.
On Fri, Oct 12, 2007 at 11:44:08PM +0200, Jan Engelhardt wrote:
>
> Allow config variables in .config to override earlier ones in the same
> file. In other words,
>
> # CONFIG_SECURITY is not defined
> CONFIG_SECURITY=y
>
> will activate it. This makes it a bit easier
On Mon, Oct 15, 2007 at 10:04:01PM -0600, Matthew Wilcox wrote:
> On Mon, Oct 15, 2007 at 07:54:22PM -0700, [EMAIL PROTECTED] wrote:
> > do PCI devices reorder their bus numbers spontaniously, or only if you
> > change the hardware?
>
> The only system I've had that reordered PCI bus numbers was
On Tuesday 16 October 2007 13:55, Eric W. Biederman wrote:
> Nick Piggin <[EMAIL PROTECTED]> writes:
> > How much swap do you have configured? You really shouldn't configure
> > so much unless you do want the kernel to actually use it all, right?
>
> No.
>
> There are three basic swapping
On Mon, Oct 15, 2007 at 07:31:54PM -0500, Rob Landley wrote:
> On Monday 15 October 2007 3:25:35 pm Geert Uytterhoeven wrote:
> > 64-bit parisc tests if /usr/bin/hppa64-linux-gnu- exists.
> > If yes, it sets CROSS_COMPILE to hppa64-linux-gnu-.
> > If no, it sets CROSS_COMPILE to hppa64-linux-
> >
On Mon, 15 Oct 2007 22:04:01 -0600
Matthew Wilcox <[EMAIL PROTECTED]> wrote:
> On Mon, Oct 15, 2007 at 07:54:22PM -0700, [EMAIL PROTECTED] wrote:
> > do PCI devices reorder their bus numbers spontaniously, or only if
> > you change the hardware?
>
> The only system I've had that reordered PCI
On Mon, 15 Oct 2007, Matthew Wilcox wrote:
On Mon, Oct 15, 2007 at 07:54:22PM -0700, [EMAIL PROTECTED] wrote:
do PCI devices reorder their bus numbers spontaniously, or only if you
change the hardware?
The only system I've had that reordered PCI bus numbers was when I had a
partitionable
On Mon, 15 Oct 2007, Eric W. Biederman wrote:
Nick Piggin <[EMAIL PROTECTED]> writes:
How much swap do you have configured? You really shouldn't configure
so much unless you do want the kernel to actually use it all, right?
No.
There are three basic swapping scenarios.
- Pushing unused
On Tuesday 16 October 2007 13:14, Eric W. Biederman wrote:
> Nick Piggin <[EMAIL PROTECTED]> writes:
> > On Monday 15 October 2007 19:16, Andrew Morton wrote:
> >> On Tue, 16 Oct 2007 00:06:19 +1000 Nick Piggin <[EMAIL PROTECTED]>
> >
> > wrote:
> >> > On Monday 15 October 2007 18:28, Christian
On Mon, Oct 15, 2007 at 07:54:22PM -0700, [EMAIL PROTECTED] wrote:
> do PCI devices reorder their bus numbers spontaniously, or only if you
> change the hardware?
The only system I've had that reordered PCI bus numbers was when I had a
partitionable system and changed the partitioning. Not
Nick Piggin <[EMAIL PROTECTED]> writes:
> On Monday 15 October 2007 18:04, Rob Landley wrote:
>> On Sunday 14 October 2007 8:45:03 pm Theodore Tso wrote:
>
>> > > excuse for conflating different categories of devices in the first
>> > > place.
>> >
>> > See the thinkpad Ultrabay drive example
This cleans up the formatting in the vDSO linker script, mostly just the
use of whitespace. It's intended to approximate the kernel standard
conventions for indenting C, treating elements of the linker script about
like initialized variable definitions.
Signed-off-by: Roland McGrath <[EMAIL
This cleans up the formatting in the vDSO linker script, mostly just the
use of whitespace. It's intended to approximate the kernel standard
conventions for indenting C, treating elements of the linker script about
like initialized variable definitions.
Signed-off-by: Roland McGrath <[EMAIL
This cleans up the formatting in the vDSO linker script, mostly just the
use of whitespace. It's intended to approximate the kernel standard
conventions for indenting C, treating elements of the linker script about
like initialized variable definitions.
Signed-off-by: Roland McGrath <[EMAIL
> There is a /proc/sys/net/ipv4/ip_dynaddr sysctl in 2.6.21.
Actually, it does look promising, thanks.
Stefan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
>> The main use for me is to deal with dangling connections due to taking
>> network interfaces up with different IP addresses (typically the wlan0
>> interface where the IP is different because I've modes from an AP to
>> another). Of course, maybe there's another way to solve this particular
>>
This cleans up the formatting in the vDSO linker script, mostly just the
use of whitespace. It's intended to approximate the kernel standard
conventions for indenting C, treating elements of the linker script about
like initialized variable definitions.
Signed-off-by: Roland McGrath <[EMAIL
On Monday, October 15, 2007 2:07 pm Henrique de Moraes Holschuh wrote:
> We should fix the backlight class to be more useful and support
> poll() or somesuch, for userspace to track the backlight level in a
> resource-friendly way for OSD (the only sane thing to do on an IBM
> thinkpad with such
Nick Piggin <[EMAIL PROTECTED]> writes:
> On Monday 15 October 2007 19:16, Andrew Morton wrote:
>> On Tue, 16 Oct 2007 00:06:19 +1000 Nick Piggin <[EMAIL PROTECTED]>
> wrote:
>> > On Monday 15 October 2007 18:28, Christian Borntraeger wrote:
>> > > Andrew, this is a resend of a bugfix patch.
On Mon, 15 Oct 2007, Stefan Richter wrote:
Subject: Re: What still uses the block layer?
Matthew Wilcox wrote:
On Mon, Oct 15, 2007 at 04:26:04AM -0500, Rob Landley wrote:
Combining USB and IDE into the same /dev/sd? namespace makes enumerating the
IDE devices much harder than in the
On Mon, 15 Oct 2007, Greg KH wrote:
On Mon, Oct 15, 2007 at 05:08:36AM -0500, Rob Landley wrote:
On Monday 15 October 2007 4:06:20 am Julian Calaby wrote:
On 10/15/07, Rob Landley <[EMAIL PROTECTED]> wrote:
I note that the eth0 and eth1 names are dynamically assigned on a first
come first
On Mon, 15 Oct 2007, Theodore Tso wrote:
On Mon, Oct 15, 2007 at 03:04:00AM -0500, Rob Landley wrote:
just
as Ethernet and PPP interfaces really are fundamentally the same
thing.
They're the same thing?
Do you mean that on a system with both, going:
ifconfig eth1 66.92.53.140
ifconfig
On Mon, Oct 15, 2007 at 08:22:31PM -0400, Chris Mason wrote:
> Hello everyone,
>
> I'm stealing the cc list and reviving and old thread because I've
> finally got some numbers to go along with the Btrfs variable blocksize
> feature. The basic idea is to create a read/write interface to
> map a
> currently against an older kernel
ah .. which older kernel?
I tried it against the broken out 2.6.23-rc8-mm2 patch set,
inserting it before the task-containersv11-* patches, but
that blew up on me - three rejected hunks.
Any chance of getting this against a current cgroup (aka
container)
> Yet by not doing any locking here to prevent a cpu from being
> hot-unplugged, you can race and allow the hot-unplug event to happen
> before calling set_cpus_allowed(). That makes this entire function a
> no-op with set_cpus_allowed() returning -EINVAL for every call, which
> isn't caught,
>From 7dd503c612afcb86b3165602ab264e2e9493b4bf Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <[EMAIL PROTECTED]>
Date: Mon, 15 Oct 2007 20:57:52 -0400
Subject: [RFC] [PATCH 2/2] capabilities: implement 64-bit capabilities
We are out of capabilities in the 32-bit capability fields, and
several
This patch is a simple cleanup which should probably be
applied to -mm (assuming I haven't messed it up). The next
patch is an experimental patch which will require userspace
support and is just RFC at this point.
>From 9fc0782de6e1287aaeebe8ad653b008f09b22c11 Mon Sep 17 00:00:00 2001
From:
On Mon, 15 Oct 2007, Dave Hansen wrote:
> diff -puN
> include/asm-mips/processor.h~PATCH_2_11_maps3-_introduce_task_size_of_for_all_arches
> include/asm-mips/processor.h
> ---
> lxc/include/asm-mips/processor.h~PATCH_2_11_maps3-_introduce_task_size_of_for_all_arches
> 2007-10-15
On Mon, 15 Oct 2007, Matt Mackall wrote:
> > The pss is going to need accessor functions, preferably inlined, and the
> > comment adjusted stating that all accesses should be through those
> > functions and not directly to the mem_size_stats struct.
> >
> > static inline u64
just found my on hand ck804, and mcp55 based AMD servers:
nmi_watchdog=1 doesn't work
but nmi_watchdog=2 does work
=1, it say: IOAPIC 8259A virtual wire mode...
Did nmi_watchdog=1 work on any other amd64 platform?
YH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Tue, 16 Oct 2007, Neil Brown wrote:
On Monday October 15, [EMAIL PROTECTED] wrote:
Therefore it is best to not have stable single-number naming schemes
for any devices on any machines. Why? Because it ensure there will
not be any second class citizens.
This is where we disagree. The
On 10/12/07, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> [ Changes since last post: fixed up lguest ]
>
> Currently, the set_lazy_mode pv_op is overloaded with 5 functions:
> 1. enter lazy cpu mode
> 2. leave lazy cpu mode
> 3. enter lazy mmu mode
> 4. leave lazy mmu mode
> 5. flush
James wrote:
> In that case, the correct fix
> is actually to move the scatterlist include from scsi_error.c (where the
> scatterlist was originally used locally) into scsi_eh.h, like this.
I suspect you're correct, yes.
--
I won't rest till it's the best ...
On Mon, 15 Oct 2007, Peter Zijlstra wrote:
>
> please pull the lockdep tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep.git
> v2.6.24-lockdep
Hmm. I'm now getting
WARNING: at kernel/lockdep.c:700 look_up_lock_class()
Call Trace:
On Mon, 2007-10-15 at 19:58 -0500, Matt Mackall wrote:
>
> > For the bits that we want to export, we could also add the unoptimized
> > access functions for any that don't already have them:
> >
> > #define __ClearPageReserved(page) __clear_bit(PG_reserved,
> > &(page)->flags)
>
>
On Mon, 2007-10-15 at 17:08 -0700, Paul Jackson wrote:
> James wrote:
> > The requirement for struct scatterlist is the same
> > before and after the gid scsi-misc patch.
>
> Not so. The git-scsi-misc.patch in 2.6.23-mm1 clearly adds the line:
>
> struct scatterlist sense_sgl;
>
> as part
On Mon, Oct 15, 2007 at 05:49:10PM -0700, Dave Hansen wrote:
> On Mon, 2007-10-15 at 19:35 -0500, Matt Mackall wrote:
> > Perhaps we need something like:
> >
> > flags = page->flags;
> > userflags =
> > FLAG_BIT(USER_REFERENCED, flags & PG_referenced) |
> > ...
> >
> > etc.
This patch accomplishes the following goals:
* kill the 'pci_enable_device ret val not checked' warning
* eliminate the incorrect mucking with pci_dev::current_state
via the following changes:
* [minor bug fix] eliminate pci_set_power_state() call in resume,
pci_enable_device() does so for
On Mon, Oct 15, 2007 at 11:10:00AM +0200, Jarek Poplawski wrote:
> On Mon, Oct 15, 2007 at 10:09:24AM +0200, Nick Piggin wrote:
> ...
> > Has performance really been much problem for you? (even before the
> > lfence instruction, when you theoretically had to use a locked op)?
> > I mean, I'd
On Mon, 2007-10-15 at 19:35 -0500, Matt Mackall wrote:
> Perhaps we need something like:
>
> flags = page->flags;
> userflags =
> FLAG_BIT(USER_REFERENCED, flags & PG_referenced) |
> ...
>
> etc. for the flags we want to export. This will let us change to
>
>
On Mon, 15 Oct 2007, Zan Lynx wrote:
On Sun, 2007-10-14 at 19:01 -0400, Rik van Riel wrote:
The kernel newbies community often gets inquiries from CS students who
need a project for their studies and would like to do something with
the Linux kernel, but would also like their code to be useful
On Mon, 15 Oct 2007, Chris Mason wrote:
> Dave reported that XFS saw much higher write throughput with large
> blocksizes, but so far I'm seeing the most benefits during reads.
Dave's tests were done with an early large blocksize patchset that had
issues with readahead. More recent versions
David,
All of your comments looked pretty valid to me. I've refreshed that
patch.
I haven't even compile-tested this so there may be some fat fingering
somewhere. I'll run compile tests on it now.
-- Dave
For the /proc//pagemap code[1], we need to able to query how
much virtual address
On Mon, 15 Oct 2007, Mark Gross wrote:
On Sun, Oct 14, 2007 at 07:01:28PM -0400, Rik van Riel wrote:
The kernel newbies community often gets inquiries from CS students who
need a project for their studies and would like to do something with
the Linux kernel, but would also like their code to
On Mon, Oct 15, 2007 at 04:34:57PM -0700, Dave Hansen wrote:
> On Mon, 2007-10-15 at 18:11 -0500, Matt Mackall wrote:
> > > Could we just have /proc/kpagereferenced? Is there a legitimate need
> > > for other flags to be visible?
> >
> > Referenced, dirty, uptodate, lru, active, slab, writeback,
On Monday 15 October 2007 3:25:35 pm Geert Uytterhoeven wrote:
> 64-bit parisc tests if /usr/bin/hppa64-linux-gnu- exists.
> If yes, it sets CROSS_COMPILE to hppa64-linux-gnu-.
> If no, it sets CROSS_COMPILE to hppa64-linux-
>
> 32-bit parisc unconditionally sets CROSS_COMPILE to hppa-linux-.
>
>
On Tue, Oct 16, 2007 at 10:03:39AM +1000, Rusty Russell wrote:
> On Tuesday 16 October 2007 08:51:17 Jeremy Fitzhardinge wrote:
> > Dave Hansen wrote:
> > > On Mon, 2007-10-15 at 17:26 -0500, Matt Mackall wrote:
> > >> +config PROC_PAGE_MONITOR
> > >> + default y
> > >> + bool "Enable
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix USB docbook warnings.
Warning(linux-2.6.23-git8//include/linux/usb/gadget.h:487): No description
found for parameter 'g'
Warning(linux-2.6.23-git8//include/linux/usb/gadget.h:506): No description
found for parameter 'g'
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix filesystems docbook warnings.
Warning(linux-2.6.23-git8//fs/debugfs/file.c:241): No description found for
parameter 'name'
Warning(linux-2.6.23-git8//fs/debugfs/file.c:241): No description found for
parameter 'mode'
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix libata docbook warnings.
Warning(linux-2.6.23-git8//drivers/ata/libata-scsi.c:3251): No description
found for parameter 'dev'
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
drivers/ata/libata-scsi.c |2 +-
1 file changed, 1 insertion(+), 1
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix kernel-api docbook warnings.
Warning(linux-2.6.23-git8//drivers/message/fusion/mptscsih.c:2618): No
description found for parameter 'sc'
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
drivers/message/fusion/mptscsih.c | 10 +++---
1 file
Hello everyone,
I'm stealing the cc list and reviving and old thread because I've
finally got some numbers to go along with the Btrfs variable blocksize
feature. The basic idea is to create a read/write interface to
map a range of bytes on the address space, and use it in Btrfs for all
metadata
On Tue, Oct 16, 2007 at 12:08:01AM +0200, Mikulas Patocka wrote:
> > On Mon, 15 Oct 2007 22:47:42 +0200 (CEST)
> > Mikulas Patocka <[EMAIL PROTECTED]> wrote:
> >
> > > > According to latest memory ordering specification documents from
> > > > Intel and AMD, both manufacturers are committed to
On Mon, Oct 15, 2007 at 04:36:38PM -0700, David Rientjes wrote:
> On Mon, 15 Oct 2007, Matt Mackall wrote:
>
> > Index: l/fs/proc/task_mmu.c
> > ===
> > --- l.orig/fs/proc/task_mmu.c 2007-10-14 13:35:31.0 -0500
> > +++
Paul Jackson wrote:
Paul M wrote:
Here's an alternative for consideration, below.
I don't see the alternative -- I just see my patch, with the added
blurbage:
#12 - /usr/local/google/home/menage/kernel9/linux/kernel/cpuset.c
# action=edit type=text
Should I be increasing my
Paul M wrote:
> Here's an alternative for consideration, below.
I don't see the alternative -- I just see my patch, with the added
blurbage:
#12 - /usr/local/google/home/menage/kernel9/linux/kernel/cpuset.c
# action=edit type=text
Should I be increasing my caffeine intake?
--
Mikulas Patocka wrote:
I know about unordered stores (movnti & similar) --- they basically use
write-combining method on memory that is normally write-back --- and they
need sfence. But which one instruction does unordered load and needs
lefence?
PREFETCHNTA.
-hpa
-
To
It isn't that hard to add simple kset attributes, so don't go through
all the gyrations of creating your own object type and show and store
functions. Just use the functions that are already present. This makes
things much simpler.
Note, the version_str string violates the "one value per file"
On Tuesday 16 October 2007 00:17, Ingo Molnar wrote:
> Linus, please pull the latest scheduler git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched.git
>
> It contains lots of scheduler updates from lots of people - hopefully
> the last big one for quite some
James wrote:
> The requirement for struct scatterlist is the same
> before and after the gid scsi-misc patch.
Not so. The git-scsi-misc.patch in 2.6.23-mm1 clearly adds the line:
struct scatterlist sense_sgl;
as part of the added struct scsi_eh_save in scsi/scsi_eh.h.
This bit me while I
On Saturday 13 October 2007 06:40:36 Jeremy Fitzhardinge wrote:
> [ Changes since last post: fixed up lguest ]
This is really nice. Thanks Jeremy!
This will conflict a little with my own churn (file movement), but no great
drama if it goes in soon.
Acked-by: Rusty Russell <[EMAIL PROTECTED]>
On Tuesday 16 October 2007 08:51:17 Jeremy Fitzhardinge wrote:
> Dave Hansen wrote:
> > On Mon, 2007-10-15 at 17:26 -0500, Matt Mackall wrote:
> >> +config PROC_PAGE_MONITOR
> >> + default y
> >> + bool "Enable /proc page monitoring" if EMBEDDED && PROC_FS &&
> >> MMU + help
> >>
From: David Brownell <[EMAIL PROTECTED]>
Date: Mon, 15 Oct 2007 16:39:10 -0700
> > Bad news, even with the rwsem after a lot more testing I can still
> > trigger the hang in ohci_hub_control() :-(
> >
> > I think we need to go back to considering the total serialization
> > approach to this
On Mon, 15 Oct 2007 19:35:30 -0400
James Bottomley <[EMAIL PROTECTED]> wrote:
> On Sat, 2007-10-13 at 22:35 -0700, Paul Jackson wrote:
> > From: Paul Jackson <[EMAIL PROTECTED]>
> >
> > The added line in scsi_eh.h:
> > struct scatterlist sense_sgl;
> > fails to compile, with the error:
> >
Andi Kleen <[EMAIL PROTECTED]> wrote:
> Stefan Monnier <[EMAIL PROTECTED]> writes:
>> The main use for me is to deal with dangling connections due to taking
>> network interfaces up with different IP addresses (typically the wlan0
>> interface where the IP is different because I've modes from an
[adding back CCs which were dropped because I'm stupid - sorry!]
On 10/16/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> On Monday 15 October 2007 5:27:55 am Julian Calaby wrote:
> > On 10/15/07, Rob Landley <[EMAIL PROTECTED]> wrote:
> > > On Monday 15 October 2007 4:06:20 am Julian Calaby wrote:
> I think the main issue with the solution you propose is that it doesn't
> deal with markers in modules, am I right ?
My suggestion applies as well to modules as anything else.
What "like Module.symvers" means is something like:
name1 vmlinux %s
name2 fs/nfs/nfs %d
All the
On Tue, 2007-10-16 at 00:03 +0200, Andi Kleen wrote:
> > Subject: [PATCH 12/12] xfs: eagerly remove vmap mappings to avoid
> > upsetting Xen
>
> This should be probably done unconditionally because it's a undefined
> dangerous condition everywhere.
Should be done unconditionally. One could
On Mon, 15 Oct 2007, Matt Mackall wrote:
> Index: l/include/asm-mips/processor.h
> ===
> --- l.orig/include/asm-mips/processor.h 2007-10-09 17:37:58.0
> -0500
> +++ l/include/asm-mips/processor.h2007-10-10
The procnames for the cpu and domain were allocated via kstrdup and so
should also be freed. The names for the files are static, but we
can differentiate them by the presence of the proc_handler. If a
kstrdup (of < 32 characters) fails the sysctl code will not see the
procname or remaining
On Monday October 15, [EMAIL PROTECTED] wrote:
> > Therefore it is best to not have stable single-number naming schemes
> > for any devices on any machines. Why? Because it ensure there will
> > not be any second class citizens.
>
> This is where we disagree. The existence of devices you
Hi. I've noticed that with recent kernels (starting somewhere between
2.6.20 and 2.6.22) I sometimes get *lots* of disk activity on resume from
suspend to ram. About 2/3 of the time, the system resumes normally but in
the remaining 1/3 of the time, the hard drive light stays on almost solid
> Bad news, even with the rwsem after a lot more testing I can still
> trigger the hang in ohci_hub_control() :-(
>
> I think we need to go back to considering the total serialization
> approach to this problem.
We shouldn't need that. What happens if you add an msleep(5)
before
On Mon, 15 Oct 2007, Matt Mackall wrote:
> Index: l/fs/proc/task_mmu.c
> ===
> --- l.orig/fs/proc/task_mmu.c 2007-10-14 13:35:31.0 -0500
> +++ l/fs/proc/task_mmu.c 2007-10-14 13:36:56.0 -0500
> @@ -122,6 +122,27
1 - 100 of 1118 matches
Mail list logo
