On Tue, Feb 27, 2007 at 07:03:21PM -0800, Michael K. Edwards ([EMAIL
PROTECTED]) wrote:
>
> State machines are much harder to write without going through a real
> on-paper design phase first. But multi-threaded code is much harder
> for a team of average working coders to write correctly, judgin
On Tue, Feb 27 2007, Adrian Bunk wrote:
> On Tue, Feb 27, 2007 at 11:02:02AM +0100, Jens Axboe wrote:
> > On Sun, Feb 25 2007, Adrian Bunk wrote:
> > > This email lists some known regressions in 2.6.21-rc1 compared to 2.6.20
> > > that are not yet fixed in Linus' tree.
> > >
> > > If you find your
* Linus Torvalds <[EMAIL PROTECTED]> [070228 06:16]:
> Anyway, I really hope the thing starts calming down now, and everybody
> should take a hard look at the regressions lists that Adrian has
> started sending out. We already fixed some of them, but there is more
> to go..
Ingo's patch correcting
On Tue, Feb 27 2007, Suparna Bhattacharya wrote:
> > It's not bad for such a high depth/batch setting, but I still wonder why
> > are results are so different. I'll look around for an x86 box with some
> > TCQ/NCQ enabled storage attached for testing. Can you pass me your
> > command line or job fi
* Jens Axboe <[EMAIL PROTECTED]> wrote:
> EngineDepth BatchBw (KiB/sec)
> libaio2 821,125
> syslet2 819,610
i'd like to do something more about this to be more in line with libaio
- if nothing
On 02/28, Srivatsa Vaddagiri wrote:
>
> On Wed, Feb 28, 2007 at 12:57:35AM +0100, Rafael J. Wysocki wrote:
> > > How about other kthread_stop()s ? For example,
> > > kernel/softirq.c:cpu_callback() ?
> >
> > They all are PF_NOFREEZE, I suppose. If we make all workqueues nonfreezable
> > (as they
On Tue, 27 Feb 2007, Eric W. Biederman wrote:
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/x86_64-mm-handle-irqs-pending-in-irr-during-irq-migration.patch
> >>
> >> That's mainly an Andi decision. Let's cc him.
> >
> > Would be good to have Eric
Hi!
> > I'm afraid this is racy. We can't touch *cwq, it may be freed. Suppose
> > that another thread does destroy_workqueue(), and we thaw that thread
> > before cwq->thread.
>
> Okay, in that case I'd suggest removing create_freezeable_workqueue() and
> make all workqueues nonfreezable once ag
Hi Andrew,
On Tue, 27 Feb 2007 12:25:51 -0800, Andrew Morton wrote:
> > On Sun, 25 Feb 2007 14:15:30 +0100 Jean Delvare <[EMAIL PROTECTED]> wrote:
> > Hi Andrew, all,
> >
> > I appear to need the following fix to be able to build 2.6.20-mm2 on
> > x86_64. Without the fix, my build attempt dies on
On Wed, Feb 28 2007, Ingo Molnar wrote:
>
> * Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> > EngineDepth Batch Bw (KiB/sec)
> > libaio 2 821,125
> > syslet 2 819,610
>
> i'd like to do something more about
On Wed, Feb 28, 2007 at 11:48:59AM +0300, Oleg Nesterov wrote:
> On 02/28, Srivatsa Vaddagiri wrote:
> > We can just thaw the worker thread selectively before kthread_stopping
> > them. This will let us freeze all worker threads (which we want to for
> > hotplug anyway).
>
> I am not sure this is
Hi,
please, review and apply to mm tree for further testing. The patch
is also available at
ftp://ftp.alsa-project.org/pub/kernel-patches/bonding-workqueue.patch .
Thank you,
Jaroslav
==
On Thu, Feb 22, 2007 at 12:31:20PM -0800, John Reiser wrote:
> This patch changes arch_setup_additonal_pages() to honor vdso_enabled.
> For i386 it also allows the option of a fixed addresss to avoid
> fragmenting the address space. Compiles and runs on i386.
> x86_64 [IA32 support] and sh maintai
> What I really object to is not the irq numbers. As an arbitrary number
> does not impose limits. What I object to is drivers that can't handle the
> full range of numbers, and the limits imposed upon those numbers when
> you require them to be indexes into an array.
>
> For talking to user spa
* K.R. Foley <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
> > i have released the v2.6.20-rt1 kernel, which can be downloaded from the
> > usual place:
> >
>
> I have a couple of questions regarding priorities of the softirqs, IRQ
> handlers, etc.
>
> With some exceptions, back in 2.6.18
* Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> > Yes. vmalloc would have the annoying side-effect of actually
> > allocating some pages which would be shadowed by the remapping, but
> > I guess get_vm_area would do the job. I'll give it a go.
>
> Hm, this is a bit awkward. We need to ma
On 02/28, Srivatsa Vaddagiri wrote:
>
> On Wed, Feb 28, 2007 at 11:48:59AM +0300, Oleg Nesterov wrote:
> > On 02/28, Srivatsa Vaddagiri wrote:
> > > We can just thaw the worker thread selectively before kthread_stopping
> > > them. This will let us freeze all worker threads (which we want to for
>
* Davide Libenzi wrote:
> > my current thinking is that special-purpose (non-programmable,
> > static) APIs like aio_*() and lio_*(), where every last cycle of
> > performance matters, should be implemented using syslets - even if
> > it is quite tricky to write syslets (which they no doubt a
On Thu, Feb 22, 2007 at 12:20:40PM +0100, Heiko Carstens wrote:
> On Thu, Feb 08, 2007 at 06:59:16PM +, Linux Kernel Mailing List wrote:
> > Commit: cfcd1705b61ecce1ab102b9593cf733fef314a19
> > Parent: 0e47e3cca100e7c8e8124378e4e44969c2e042fd
> > Author: David Woodhouse <[EMAIL PROT
On Wed, 2007-02-28 at 07:43 +0100, Benjamin Herrenschmidt wrote:
> I wouldn't be that sure ... I've had problems in the past with PMU based
> cpufreq... looks like flushing all caches and hard-resetting the
> processor on the fly when there can be pending DMAs might be a source of
> trouble... espe
Linus,
could you please pull from 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive updates for HID core layer and USB HID for 2.6.21-rc2. These
are mainl
The test which automatically enables the backup timer on some HP
machines doesn't trigger on other hardware which needs the backup
timer too.
This patch add a way to enable it manually (8250.use_backup_timer=1)
to deal with these machines.
Signed-off-by: Gerd Hoffmann <[EMAIL PROTECTED]>
Cc: Alex
Hi Antonino :)
* Antonino A. Daplas <[EMAIL PROTECTED]> dixit:
> On Mon, 2007-02-26 at 21:32 +0100, DervishD wrote:
> > Probably setting it back to 4096 will make the problem reappear.
> > Right now I cannot test, but I'll make some experiments.
>
> Can you try this patch? It might help
On Wednesday, 28 February 2007 02:23, Srivatsa Vaddagiri wrote:
> On Wed, Feb 28, 2007 at 12:53:14AM +0300, Oleg Nesterov wrote:
> > I think it is good. Srivatsa?
>
> Maybe additional comments on why we don't skip vfork kernel tasks may be
> good.
Which is because we don't want the kernel threa
On 02/28, Rafael J. Wysocki wrote:
>
> On Wednesday, 28 February 2007 02:23, Srivatsa Vaddagiri wrote:
> > On Wed, Feb 28, 2007 at 12:53:14AM +0300, Oleg Nesterov wrote:
> > > I think it is good. Srivatsa?
> >
> > Maybe additional comments on why we don't skip vfork kernel tasks may be
> > good.
On Wed, Feb 28, 2007 at 11:57:27AM +0100, Rafael J. Wysocki wrote:
> Which is because we don't want the kernel threads to be frozen in unexpected
> places, so we allow them to block freeze_processes() instead or to set
> PF_NOFREEZE?
Looks good!
--
Regards,
vatsa
-
To unsubscribe from this list:
On Wednesday, 28 February 2007 02:14, Nigel Cunningham wrote:
> Hi.
>
> On Wed, 2007-02-28 at 01:08 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, 28 February 2007 01:01, Johannes Berg wrote:
> > > On Wed, 2007-02-28 at 00:57 +0100, Rafael J. Wysocki wrote:
> > >
> > > > Okay, in that case I'd
On Wednesday, 28 February 2007 10:10, Srivatsa Vaddagiri wrote:
> On Wed, Feb 28, 2007 at 11:48:59AM +0300, Oleg Nesterov wrote:
> > On 02/28, Srivatsa Vaddagiri wrote:
> > > We can just thaw the worker thread selectively before kthread_stopping
> > > them. This will let us freeze all worker thread
On Wednesday, 28 February 2007 04:51, Srivatsa Vaddagiri wrote:
> On Wed, Feb 28, 2007 at 08:31:13AM +0530, Srivatsa Vaddagiri wrote:
> > This problem (of kthread_stopping a frozen thread) was there when we
> > implemented freezer-based cpu hotplug. We worked around that in the
> > callbacks by tha
On Tuesday 27 February 2007 17:03, Davide Libenzi wrote:
> On Tue, 27 Feb 2007, Eric Dumazet wrote:
> > On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
> > > Epoll is doing multiple passes over the ready set at the moment,
> > > because of the constraints over the f_op->poll() call. Lookin
John wrote:
Andi Kleen wrote:
John wrote:
My app expects a stream of UDP datagrams containing compressed video.
These datagrams have been time stamped by the source using a high
resolution clock.
Why do you need another time stamp then?
Source and receiver do not share a common clock. Th
In wireless we'd like to allow renaming of the phy devices we surface in
sysfs. The base wireless code, however, can be built modular and thus we
need device_rename exported.
Signed-off-by: Johannes Berg <[EMAIL PROTECTED]>
---
Is this acceptable? For testing reasons we want the cfg80211 code
bui
> > Would you use MD at all, taking in account the disks come from the
> > same batch and all? I hear these things about MD/RAID being pointless
> > when you use disks from the same brand/type/batch since they most
> > likely will break shortly after each other.
>
> Well, for values of "shortly" i
> The bidirectional use is/was PL/IP, aka "laplink" connections. Yes, I
> still have a machine I installed that way, and it will run 2.2.19
> forever before I try it again. ;-)
PLIP/Laplink runs bidirectional on ordinary parallel ports. The
bidirectional part of parallel ports in "normal" modes
22 Şub 2007 Per tarihinde, S.Çağlar Onur şunları yazmıştı:
> 22 Şub 2007 Per tarihinde, Antonino A. Daplas şunları yazmıştı:
> > Ah, and you have fb_splash too. That's why the tracing was not what I
> > expected it to be.
> >
> > Try using video=vesafb:noblank to disable hardware blanking and fin
On Tue, Feb 27 2007, Xiaoning Ding wrote:
> Hi,
>
> I am reading the source code AS scheduler in 2.6.18(as-ioscheduler.c).
> In function as_close_req, variable delay is in millisecond, while
> ad->antic_expire is in jiffies. Doesn't the comparison of delay and
> ad->antic_expire make any problem?
On Wed, Feb 28 2007, Tony Breeds wrote:
> On Tue, Feb 27, 2007 at 03:33:34PM +0100, Jens Axboe wrote:
>
> > It looks ok (better than end_request()), though it would still be nice
> > to properly end requests. See the recent thread on the lguest block
> > driver.
>
> Hi Jens,
> I read throug
On Tue, Feb 27 2007, Swetha Krishnan wrote:
> I'm using linux 2.6.12 within user-mode linux. I need to remove a
> specific I/O request (that I have means to identify) from the I/O
> scheduler queues instead of moving it to the driver dispatch queue.
> To remove a request from the anticipatory sch
On 02/28/2007 02:04 PM, Alan wrote:
PLIP/Laplink runs bidirectional on ordinary parallel ports. The
bidirectional part of parallel ports in "normal" modes is still used
for things like PnP detection of printer and drivers.
And my parallel port Iomega ZIP drive, it seems. I actually checked
e
Zwane Mwaikambo <[EMAIL PROTECTED]> writes:
> Hi Eric,
> Thanks for getting this cruft cleaned up. I have a few comments
> regarding;
>
> handle-irqs-pending-in-irr-during-irq-migration.patch
>
> 1) It relies on checking the IRR, this could race with the corresponding
> vector bit being se
> --- devices-2.6+.txt 2007-02-22 13:37:18.0 -0600
> +++ devices-2.6+.new 2007-02-22 13:42:50.0 -0600
> @@ -2770,7 +2770,10 @@
>45 = /dev/ttyMM1 Marvell MPSC - port 1
>46 = /dev/ttyCPM0 PPC CPM (SCC or SMC) -
port 0
>
hello,
Can someone tell me what this means?
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen
ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288
out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: port is slow to respond, ple
Hello,
This patch splits the vlan_group struct into a multi-allocated struct. On
x86_64, the size of the original struct is a little more than 32KB, causing
a 4-order allocation, which is prune to problems caused by buddy-system
external fragmentation conditions.
I couldn't just use vmalloc() be
acpi_fan_suspend should probably set state to ACPI_D3, rather than ACPI_D0.
With this change the fan works after S3 suspend atleast on HP nw8000 laptop,
for which the suspended fan has been broken since sword-and-stone.
Signed-off-by: Tommi Kyntola <[EMAIL PROTECTED]>
---
Why this was ACPI_D0 be
Mathiasen, Torben wrote:
Got around looking at this one. I'm fine with this approach, but the
CPM5 fix looks wrong. Shouldn't it be:
49 = /dev/ttyCPM3 PPC CPM (SCC or SMC) - port 3
instead?
Well, how many CPM devices can exist? If there are really 6 ports
possible, they need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I rebuild the kernel, without the git-block patches Patches
revert-md-avoid-possible-bug_on-in-md-bitmap-handling-for-git-block.patch
git-block.patch
git-block-fixup.patch
git-block-dupe-definitions.patch
git-block-xfs-barriers-broke.patch
but i stil
Brice Goglin <[EMAIL PROTECTED]> writes:
> Linus Torvalds wrote:
>> Oh well.. I'm not very proud of this, because quite frankly, -rc2 has way
>> more changes than I really like.
>>
>
> Hi Linus,
>
> rc2 fails to build on my thinkpad t43:
>
> CC arch/i386/kernel/io_apic.o
> arch/i386/ker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I rebuild the kernel, without the git-block patches Mr. Piotrowski wrote:
revert-md-avoid-possible-bug_on-in-md-bitmap-handling-for-git-block.patch
git-block.patch
git-block-fixup.patch
git-block-dupe-definitions.patch
git-block-xfs-barriers-broke.pat
> Mathiasen, Torben wrote:
> >
> > Got around looking at this one. I'm fine with this approach, but the
> > CPM5 fix looks wrong. Shouldn't it be:
> >
> > 49 = /dev/ttyCPM3 PPC CPM (SCC or SMC) - port 3
> >
> > instead?
> >
>
> Well, how many CPM devices can exist? If there are really 6
On Wed, Feb 28, 2007 at 12:11:03PM +0100, Rafael J. Wysocki wrote:
> > In addition to thawing worker thread before kthread_stopping it, there
> > are minor changes required in worker threads, to check for
> > is_cpu_offline(bind_cpu) when they come out of refrigerator and jump to
> > wait_to_die if
On 2/28/07, Jens Axboe <[EMAIL PROTECTED]> wrote:
On Tue, Feb 27 2007, Xiaoning Ding wrote:
> Hi,
>
> I am reading the source code AS scheduler in 2.6.18(as-ioscheduler.c).
> In function as_close_req, variable delay is in millisecond, while
> ad->antic_expire is in jiffies. Doesn't the comparison
Ingo Molnar wrote:
> * K.R. Foley <[EMAIL PROTECTED]> wrote:
>
>> Ingo Molnar wrote:
>>> i have released the v2.6.20-rt1 kernel, which can be downloaded from the
>>> usual place:
>>>
>> I have a couple of questions regarding priorities of the softirqs, IRQ
>> handlers, etc.
>>
>> With some excep
On Wednesday 28 February 2007, Eric W. Biederman wrote:
> Arnd Bergmann <[EMAIL PROTECTED]> writes:
>
> >
> > Introducing the irq_request() etc. functions that take a struct irq*
> > instead of an int sounds good, but I'd hope we can avoid using those
> > in device drivers and do a separate abstra
pci: each device/function has a unique irq, drivers need not know
about it afaics.
Then there is msi and with msi-x you can have up to 4K irqs.
I have to admit I still don't really understand how this works
at all. Can a driver that uses msi-x have different handlers
for each of those inte
* Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
> >> +#ifdef CONFIG_PARAVIRT
> >> +/* After pte_t, etc, have been defined */
> >> +#include
> >> +#endif
> >>
> >
> > hm - there's already a CONFIG_PARAVIRT conditional in
> > asm-i386/paravirt.h.
>
> Yes, but it happens after asm/paravirt.
This is updated version of patch aimed to fix direct_io error handling issue
i've previously sent 2 wheeks ago. If you don't like anything in this patch
plese let me know.
Changes:
- comments added. I think now it is clearly describe things.
- patch prepared against 2.6.20-mm2
How this patch
On Wed, Feb 28, 2007 at 06:47:21PM +0530, Srivatsa Vaddagiri wrote:
> --- workqueue.c.org 2007-02-28 18:32:48.0 +0530
> +++ workqueue.c 2007-02-28 18:44:23.0 +0530
> @@ -718,6 +718,8 @@ static void cleanup_workqueue_thread(str
> insert_wq_barrier(cwq, &barr, 1)
Florin Iucha wrote:
On Tue, Feb 27, 2007 at 09:36:23PM -0500, Bill Davidsen wrote:
Florin Iucha wrote:
Hello, it's me and my 70 GB of photos again.
I have tested both CIFS and NFSv4 clients in kernel 2.6.20-rc1 . CIFS
passed with flying colors and NFSv4 stalled after 7 GB.
On Wed, Feb 28 2007, Benoit Boissinot wrote:
> On 2/28/07, Jens Axboe <[EMAIL PROTECTED]> wrote:
> >On Tue, Feb 27 2007, Xiaoning Ding wrote:
> >> Hi,
> >>
> >> I am reading the source code AS scheduler in 2.6.18(as-ioscheduler.c).
> >> In function as_close_req, variable delay is in millisecond, wh
This series of patches extend the alternative instructions framework on
i386 and x86_64 architectures to support two alternative instruction
replacements. This code is used together with the introduction of the
X86_FEATURE_SYNC_RDTSC flag on i386 to simplify and optimize the
get_cycles_sync() funct
From: Joerg Roedel <[EMAIL PROTECTED]>
This patch extends the alternative instructions framework to support 2
alternative instructions.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
--
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG
diff --git a/arch/i386/kernel/alternat
Hi,
I have a question concerning the line discipline behaviour for serial
devices.
When the line discipline is set via ioctl from user space to e.g. N_PPP and
the userspace program returns without resetting the line discipline back to
N_TTY, the serial device cannot be used (ENODV) until an ap
From: Joerg Roedel <[EMAIL PROTECTED]>
In this patch updates the x86_64 architecture to work with the changes
to alternative instructions in i386
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
--
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG
diff --git a/arch/x86_64/lib
From: Joerg Roedel <[EMAIL PROTECTED]>
This patch simplifies the get_cycles_sync() function by removing the
#ifdefs from it. Further it introduces an optimization for AMD
processors. There the RDTSCP instruction is used instead of CPUID;RDTSC
which is helpfull if the kernel runs as a KVM guest. Ru
A change early last year reordered struct page so that ptl overlaps not only
private, but also mapping. Since spinlock_t can be much larger, I'm wondering
whether there's a reason to not also overlay the space index and lru take -
are these used for anything on page table pages?
Thanks, Jan
-
To u
On Wed, 28 Feb 2007 14:47:12 +0100
Christopher Meller <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a question concerning the line discipline behaviour for serial
> devices.
> When the line discipline is set via ioctl from user space to e.g. N_PPP and
> the userspace program returns without reset
On Feb 28, 2007, at 7:14 AM, Mathiasen, Torben wrote:
Mathiasen, Torben wrote:
Got around looking at this one. I'm fine with this approach, but the
CPM5 fix looks wrong. Shouldn't it be:
49 = /dev/ttyCPM3 PPC CPM (SCC or SMC) - port 3
instead?
Well, how many CPM devices can
Segher Boessenkool wrote:
46 = /dev/ttyCPM0PPC CPM (SCC or SMC) - port 0
...
- 47 = /dev/ttyCPM5PPC CPM (SCC or SMC) - port 5
+ 49 = /dev/ttyCPM5PPC CPM (SCC or SMC) - port 5
If CPM0 is 46, then CPM5 is not 47, but not 49 either.
Un
On 2/27/07, Veronique & Vincent <[EMAIL PROTECTED]> wrote:
Maybie the Fedora team should use the asound.conf configuration instead?
This doesn't work for apps that use the deprecated /dev/dsp API.
Of course, a modern distro should be trying to purge these anyway...
Lee
-
To unsubscribe from t
H. Peter Anvin wrote:
Also, if QE really is just CPM v3, and they share the same minors, why
change the name?
Because the QE isn't called CPM v3, that's just one way to think about
it. It's a different device that has some backwards compatibility, but
the drivers are all distinct and they a
On Wed, 28 Feb 2007, Robert Hancock wrote:
> Gerhard Mack wrote:
> > hello,
> > Can someone tell me what this means?
> > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen
> > ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288
> > out
> > res 40/
>
> Mathiasen, Torben wrote:
>
> > Assuming QE has 4 entries, I would expect CPM to be the same. But we
> > need verification of that. If it needs 6, we are in more trouble.
>
> The QE can have up to 8, actually, but I'm willing to limit the driver
> to 4.
Its your choice if you want to limit i
From: Joerg Roedel <[EMAIL PROTECTED]>
This patch adds the X86_FEATURE_SYNC_RDTSC to the i386 architecture.
This is very helpfull to simplify the get_cycles_sync() function and
remove the #ifdefs from it.
Signed-off-by: Joerg Roedel <[EMAIL PROTECTED]>
--
Joerg Roedel
Operating System Research
Gerhard Mack wrote:
hello,
Can someone tell me what this means?
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen
ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288
out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1: port
Gerhard Mack wrote:
ata1.00: configured for UDMA/100
[...]
ata1.00: configured for UDMA/66
[...]
ata1.00: configured for UDMA/44
[...]
ata1.00: configured for UDMA/33
[...]
ata1.00: configured for UDMA/25
[...]
ata1.00: configured for UDMA/16
[...]
ata1.00: configured for PIO4
I have the same p
On Feb 28, 2007, at 8:51 AM, Mathiasen, Torben wrote:
Mathiasen, Torben wrote:
Assuming QE has 4 entries, I would expect CPM to be the same. But we
need verification of that. If it needs 6, we are in more trouble.
The QE can have up to 8, actually, but I'm willing to limit the
driver
to
On Wed, 28 Feb 2007, Tomas Carnecky wrote:
> Gerhard Mack wrote:
> > ata1.00: configured for UDMA/100
> > [...]
> > ata1.00: configured for UDMA/66
> > [...]
> > ata1.00: configured for UDMA/44
> > [...]
> > ata1.00: configured for UDMA/33
> > [...]
> > ata1.00: configured for UDMA/25
> > [...]
> >
Kumar Gala wrote:
On Feb 28, 2007, at 8:51 AM, Mathiasen, Torben wrote:
Mathiasen, Torben wrote:
Assuming QE has 4 entries, I would expect CPM to be the same. But we
need verification of that. If it needs 6, we are in more trouble.
The QE can have up to 8, actually, but I'm willing to lim
[adding Andi and Ingo]
John Reiser wrote:
> Architectures such as i386, sh, x86_64 have a flag /proc/sys/vm/vdso_enabled
> to choose whether the kernel should setup a process to use vdso after
> execve().
> Informing the user code via AT_SYSINFO* is controlled by macro ARCH_DLINFO in
> fs/binfmt_
How does this look? The new and improved display class.
Signed-Off: James Simmons <[EMAIL PROTECTED]>
diff -urN -X fbdev-2.6/Documentation/dontdiff
linus-2.6/drivers/video/display/display-sysfs.c
fbdev-2.6/drivers/video/display/display-sysfs.c
--- linus-2.6/drivers/video/display/display-sysfs
openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to
require a password to unlock, but it asks for password. When the screen
unlocks, kwin is gone with no errors logged in /var/log/kdm or
/var/log/messages. No problems with 2.6.20.
Same problem on openSUSE 10.2 x86_64, KDE-3.5.5 a
Ralf Müller wrote:
I had the same type of problem using an unstable power supply - after
replacing it the problems
were gone ...
Hm.. my shuttle box has only a 350W power supply, that could indeed be
the problem, as I have an Athlon 64 X2 4400+ CPU (dual core), two
SATA-II 500GB harddrives
On Wed, 28 Feb 2007, Eric Dumazet wrote:
> On Tuesday 27 February 2007 17:03, Davide Libenzi wrote:
> > On Tue, 27 Feb 2007, Eric Dumazet wrote:
> > > On Tuesday 27 February 2007 03:32, Davide Libenzi wrote:
> > > > Epoll is doing multiple passes over the ready set at the moment,
> > > > because o
Jens Axboe wrote:
On Wed, Feb 28 2007, Benoit Boissinot wrote:
On 2/28/07, Jens Axboe <[EMAIL PROTECTED]> wrote:
On Tue, Feb 27 2007, Xiaoning Ding wrote:
Hi,
I am reading the source code AS scheduler in 2.6.18(as-ioscheduler.c).
In function as_close_req, variable delay is in millisecond, whi
Mathiasen, Torben wrote:
Assuming QE has 4 entries, I would expect CPM to be the same. But we
need verification of that. If it needs 6, we are in more trouble.
The QE can have up to 8, actually, but I'm willing to limit the driver
to 4.
-
To unsubscribe from this list: send the line "unsubsc
On Wednesday 28 February 2007 17:19, Sid Boyce wrote:
> openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to
> require a password to unlock, but it asks for password. When the screen
> unlocks, kwin is gone with no errors logged in /var/log/kdm or
> /var/log/messages. No problems wi
Hi!
> > If kernelspace rescheduling is that fast, then please explain me why
> > userspace one always beats kernel/userspace?
>
> because 'user space scheduling' makes no sense? I explained my thinking
> about that in a past mail:
...
> 2) there has been an IO event. The thing is, for IO event
Hi!
> > I think what you are not hearing, and what everyone else is saying
> > (INCLUDING Linus), is that for most programmers, state machines are
> > much, much harder to program, understand, and debug compared to
> > multi-threaded code. You may disagree (were you a MacOS 9 programmer
> > in an
On Wed, 28 Feb 2007, Ingo Molnar wrote:
>
> * Davide Libenzi wrote:
>
> > Why can't aio_* be implemented with *simple* (or parallel/unrelated)
> > syscall submit w/out the burden of a complex, limiting and heavy API
>
> there are so many variants of what people think 'asynchronous IO' should
Kumar Gala wrote:
Its your choice if you want to limit it to 4 or have it moved into a
different minor range. I can live with both.
I'd rather we support 8 now.
Ok, a different minor range it is, then. 192-199?
--
Timur Tabi
Linux Kernel Developer @ Freescale
-
To unsubscribe from this lis
>>/ openSUSE 10.3 Alpha and KDE-3.5.6, xorg-x11-7.2. KDE is setup not to/
>>/ require a password to unlock, but it asks for password. When the
screen/
>>/ unlocks, kwin is gone with no errors logged in /var/log/kdm or/
>>/ /var/log/messages. No problems with 2.6.20./
>>
>>/ Same problem on openS
H. Peter Anvin wrote:
It sounds like the QE driver should be moved to a separate minor range,
and given 8 minors.
I just had a thought - since udev doesn't care about major/minor number assignments, can
we say that the limit is 4 devices if you're not using udev, and 8 otherwise?
--
Timur T
I guess most stack corruptions touch only a small part of the stack.
These kinds of corruptions can only be detected from inside the
program.
Anyway, going beyond the program's stack boundaries would fault the program.
Checking the threadinfo constantly it'll be (IMHO) mostly useless...
On 2/2
the backlight on my thinkpad still (2.6.20 worked fine) doesn't come
on if i have the radeon backlight enabled. without it, i guess it's
the ibm acpi modules that controls the backlight and it seems to work
fine.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
|
Timur Tabi wrote:
H. Peter Anvin wrote:
It sounds like the QE driver should be moved to a separate minor
range, and given 8 minors.
I just had a thought - since udev doesn't care about major/minor number
assignments, can we say that the limit is 4 devices if you're not using
udev, and 8 oth
On 2/27/07, Fausto Carvalho <[EMAIL PROTECTED]> wrote:
Well, i have a 8042 controller "connected" to the keyboard controller
that send information about battery and others to the keyboard
interrupt and io ports in the format of keystrokes. I want a way to
not alter atkbd but to create another dri
Yes. I goofed, and missed that stupid case. The offending lines
should just die. Patch already sent to Linus.
Could the patch be posted? or could I see a git commit so I can get it myself?
Thanks,
David Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
On Wed, 28 Feb 2007, Davide Libenzi wrote:
>
> At this point, given how threadlets can be easily/effectively dispatched
> from userspace, I'd argue the presence of either single/parallel or syslet
> submission altogether. Threadlets allows you to code chains *way* more
> naturally than syslet
> I'm not sure I understand. What the current implementation does is to
> use host based framebuffer memory. Apps mmap that memory and draw to
> that. Then after the delay, that framebuffer is written to the
> device's memory. That's the scenario for hecubafb where the Apollo
> controller maintain
Quick question. Can this board initialize more than one graphics card?
On Wed, 21 Feb 2007, Brandon Howard wrote:
> Oops, forgot to include the relevant links in the previous email:
>
> [1]
> http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2287
> [2] http://www.
1 - 100 of 364 matches
Mail list logo
