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.
Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes:
>> 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
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, , 1);
>
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
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
> 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
-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
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
>
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
-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
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
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
On Wednesday, 28 February 2007 01:27, Kristian Grønfeldt Sørensen wrote:
> On Tue, 2007-02-27 at 23:30 +0100, Rafael J. Wysocki wrote:
> > On Tuesday, 27 February 2007 23:04, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > On Tuesday, 27 February 2007 19:45, Kristian Grønfeldt Sørensen wrote:
> >
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()
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,
> --- 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
>
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
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
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
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
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
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?
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
> 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
> > 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"
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
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.
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.
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
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
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
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
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 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
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
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:
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
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
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...
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
* 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
On Wed, Feb 28, 2007 at 10:34:37AM +0100, Jarek Poplawski wrote:
> On 28-02-2007 02:27, Jean Tourrilhes wrote:
...
> > + /* This function is only used for network interface.
> > +* Some hotplug package track interfaces by their name and
> > +* therefore want to know when the name is
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
>
On 28-02-2007 02:27, Jean Tourrilhes wrote:
> Hi all,
...
> Patch for 2.6.20 is attached. The patch was tested on a system
> running the hotplug scripts, and on another system running udev.
>
> Have fun...
>
> Jean
>
> Signed-off-by: Jean Tourrilhes <[EMAIL PROTECTED]>
>
Hi,
> >
> > +static inline int ehea_hash_skb(struct sk_buff *skb, int num_qps)
> > +{
> > + u32 tmp;
> > + if ((skb->nh.iph->protocol == IPPROTO_TCP)
> > + && skb->protocol == ETH_P_IP) {
>
> skb->protocol has network byte order. The ETH_P_IP test should also
> logically come before
Hi,
> Patch for 2.6.20 is attached.
... and in the meantime netdevices aren't class_device any more :) IOW,
your patch isn't going to work any more. Also, I think wireless could
benefit from this as well.
> The kobject framework is well designed, so adding these
> features is
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
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 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
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
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
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
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
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
* 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
* 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
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
* 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
* 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
* 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
> 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
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
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,
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, judging
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 name in the
* 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 a
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 file
* 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 were
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 also ack
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 again for
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:
In
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 this to be
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 a good
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
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 space I
* 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 and prior
* 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 map the
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
hotplug
* Davide Libenzi davidel@xmailserver.org 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
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 PROTECTED]
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...
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
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 with
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 threads to
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.
Which is
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 suggest
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 threads (which
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 thawing
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. Looking at the
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.
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
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 in months in
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 is
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 find out
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?
The
301 - 400 of 728 matches
Mail list logo
