James Bottomley wrote:
On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
I can't even say if the tapes are written correctly as I can't read them
(one does not reboot production machines back to 2.4.x just to try to
read a backup tape - I don't have 2.6.x older than 2.6.20 on these
Mike Christie wrote:
James Bottomley wrote:
On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
I can't even say if the tapes are written correctly as I can't read them
(one does not reboot production machines back to 2.4.x just to try to
read a backup tape - I don't have 2.6.x older than
On Monday, 19 March 2007 16:32, Pavel Machek wrote:
I have the same problem on my IBM X60s on rc1 and rc2. Can't resume
from RAM, can't suspend to disk. It is possible to revert all the
changes to ACPI and test it?
This is with CONFIG_KVM=n?
Yes.
I've
On Fri, Mar 16, 2007 at 04:00:31PM -0700, Greg KH wrote:
That's because it doesn't apply at all to the current 2.6.20.3 kernel
tree. Can you rediff it for that one so that we can apply it properly?
My apologies - that depended on a previous patch which I thought had
made it into -stable.
-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike [EMAIL PROTECTED]
x86_64 needs some TLS fixes. What was missing was remembering the child
thread id during clone and stuffing it into the child during each context
switch.
The %fs value
On Monday 19 March 2007, James Bottomley wrote:
On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
I can't even say if the tapes are written correctly as I can't read
them (one does not reboot production machines back to 2.4.x just to
try to read a backup tape - I don't have 2.6.x older
On Mon, 2007-03-19 at 17:47 -0400, Gene Heskett wrote:
James, could this also be the cause of a tar based backup going crazy and
thinking all data is new under any 2.6.21-rc* kernel I've tested so far
with amanda, which in my case uses tar? I've tried the fedora patched
tar-1.15-1, and one
On Sun, Mar 18, 2007 at 12:42:00PM +0200, Avi Kivity wrote:
Heiko Carstens wrote:
In addition, if we would port kvm to s390, then we would need to
make sure that each virtual cpu only gets executed from the thread
that created it. That is simply because the upper half of our page
tables
Heiko Carstens wrote:
Right. I agree it's more natural to associate a vcpu with a task
instead of a vcpu being an independent entry. We'd still need a
handle for it, and in Linux that's an fd (pid doesn't cut it as it's
racy, and probably slower too as it has to go through a global structure).
On Mon, Mar 19, 2007 at 06:02:57PM +0200, Avi Kivity wrote:
Heiko Carstens wrote:
I agree with all of the above, and in addition, integration to the
scheduler will allow us to reduce vcpu migration rate, and maybe do
things like gang scheduling.
But that doesn't mean it can be done now: we
Avi Kivity wrote:
So the plan is:
- get the /dev/kvm ABI into 2.6.22
- implement smp
- add another arch
- move to a syscall based interface in parallel; userspace should work
with both
- deprecate the old ABI and external modules.
I would also like to add using arbitrary vmas as guest
Thank you James.
I will submit new patch that will throttle (if required) from
eh_timed_out call back.
Regards,
Sumant
-Original Message-
From: James Bottomley [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 3:23 PM
To: Patro, Sumant
Cc: [EMAIL PROTECTED];
Mike Christie wrote:
James Bottomley wrote:
On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
I can't even say if the tapes are written correctly as I can't read them
(one does not reboot production machines back to 2.4.x just to try to
read a backup tape - I don't have 2.6.x older than
Mike Christie wrote:
Mike Christie wrote:
James Bottomley wrote:
On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
I can't even say if the tapes are written correctly as I can't read them
(one does not reboot production machines back to 2.4.x just to try to
read a backup tape - I don't
On Sun, 18 Mar 2007 19:35:48 +0100
Michal Piotrowski [EMAIL PROTECTED] wrote:
WARNING: could not find versions for .tmp_versions/built-in.mod
WARNING: could not find versions for .tmp_versions/built-in.mod
WARNING: could not find versions for .tmp_versions/built-in.mod
WARNING: could not find
On 03/20, Oleg Nesterov wrote:
On 03/19, Davide Libenzi wrote:
I'd need a get_task_struct in any case in order to safely call
unlock_task_sighand(). At that point I'd prefer to just pass through the
struct pid*. I'll be posting the new version for review as soon as I
complete a few
Got this from a nfs booted 2.6.20.3 x86 system (complete diskless boot):
BUG: at fs/nfs/pagelist.c:339 nfs_scan_dirty()
[c017b1cc] nfs_scan_dirty+0x17e/0x18a
[c013407a] generic_writepages+0x224/0x2b6
[c017e116] nfs_wait_on_requests_locked+0x80/0x8e
[c017f56f] nfs_sync_mapping_wait+0x9d/0x14b
Pekka J Enberg wrote:
From: Pekka Enberg [EMAIL PROTECTED]
This changes kmem_cache_free() to deal with NULL objects passed to it. The
current behavior is inconsistent with kfree() so there are callers
passing NULL to kmem_cache_free().
Andreas, can you please confirm this fixes the oops
On Tue, 20 Mar 2007, Oleg Nesterov wrote:
On 03/20, Oleg Nesterov wrote:
On 03/19, Davide Libenzi wrote:
I'd need a get_task_struct in any case in order to safely call
unlock_task_sighand(). At that point I'd prefer to just pass through the
struct pid*. I'll be posting the new
Quicklists for page table pages V3
V2-V3
- Fix Kconfig issues by setting CONFIG_QUICKLIST explicitly
and default to one quicklist if NR_QUICK is not set.
- Fix i386 support. (Cannot mix PMD and PTE allocs.)
- Discussion of V2.
http://marc.info/?l=linux-kernelm=117391339914767w=2
V1-V2
- Add
Quicklist for IA64
IA64 is the origin of the quicklist implementation. So cut out the pieces
that are now in core code and modify the functions called.
Signed-off-by: Christoph Lameter [EMAIL PROTECTED]
Index: linux-2.6.21-rc3-mm2/arch/ia64/mm/init.c
From: David Miller [EMAIL PROTECTED]
[QUICKLIST]: Add sparc64 quicklist support.
I ported this to sparc64 as per the patch below, tested on
UP SunBlade1500 and 24 cpu Niagara T1000.
Signed-off-by: David S. Miller [EMAIL PROTECTED]
Index: linux-2.6.21-rc3-mm2/arch/sparc64/Kconfig
i386: Convert to quicklists
Implement the i386 management of pgd and pmds using quicklists.
The i386 management of page table pages currently uses page sized slabs.
Getting rid of that using quicklists allows full use of the page flags
and the page-lru. So get rid of the improvised linked lists
Conver x86_64 to using quicklists
This adds caching of pgds and puds, pmds, pte. That way we can
avoid costly zeroing and initialization of special mappings in the
pgd.
A second quicklist is used to separate out PGD handling. Thus we can carry
the initialized pgds of terminating processes over
On Thu, 08 Mar 2007 23:01:13 +
David Woodhouse [EMAIL PROTECTED] wrote:
Most system calls seem to get added to i386 first. This patch
automatically generates a warning for any new system call which is
implemented on i386 but not the architecture currently being compiled.
On PowerPC at the
On Thu, 15 Mar 2007 07:54:14 -0700 Greg KH wrote:
On Thu, Mar 15, 2007 at 11:19:20AM +0100, Mike Galbraith wrote:
On Thu, 2007-03-15 at 01:06 -0700, Greg KH wrote:
That's good. But why don't we have a module name for this driver?
And if we don't have a module name, why would
This patch add an anonymous inode source, to be used for files that need
and inode only in order to create a file*. We do not care of having an
inode for each file, and we do not even care of having different names in
the associated dentries (dentry names will be same for classes of file*).
This patch wire the signalfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/arch/i386/kernel/syscall_table.S
===
---
This is an example about how to add eventfd support to the current KAIO code,
in order to enable KAIO to post readiness events to a pollable fd
(hence compatible with POSIX select/poll). The KAIO code simply signals
the eventfd fd when events are ready, and this triggers a POLLIN in the fd.
This
This patch introduces a new system call for timers events delivered
though file descriptors. This allows timer event to be used with
standard POSIX poll(2), select(2) and read(2). As a consequence of
supporting the Linux f_op-poll subsystem, they can be used with
epoll(2) too.
The system call is
This patch wire the timerfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/arch/i386/kernel/syscall_table.S
===
---
This patch wire the eventfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/arch/i386/kernel/syscall_table.S
===
---
This patch wire the eventfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/arch/x86_64/ia32/ia32entry.S
===
---
This patch implement the necessary compat code for the timerfd system call.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/fs/compat.c
===
---
This is a very simple and light file descriptor, that can be used as
event wait/dispatch by userspace (both wait and dispatch) and by the
kernel (dispatch only). It can be used instead of pipe(2) in all cases
where those would simply be used to signal events. Their kernel overhead
is much lower
This patch implement the necessary compat code for the signalfd system call.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/fs/compat.c
===
---
This patch wire the timerfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/arch/x86_64/ia32/ia32entry.S
===
---
This patch wire the signalfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi davidel@xmailserver.org
- Davide
Index: linux-2.6.21-rc3.quilt/include/asm-x86_64/unistd.h
===
---
On Mon, 19 Mar 2007 15:37:16 -0800 (PST)
Christoph Lameter [EMAIL PROTECTED] wrote:
This patchset introduces an arch independent framework to handle lists
of recently used page table pages to replace the existing (ab)use of the
slab for that purpose.
1. Proven code from the IA64 arch.
Has
On Mon, 19 Mar 2007, Andrew Morton wrote:
Has it been proven that quicklists are superior to simply going direct to the
page allocator for these pages?
Yes.
Would it provide a superior solution if we were to a) stop zeroing out the
pte's when doing a fullmm==1 teardown and b) go direct to
From: Andrew Morton [EMAIL PROTECTED]
Date: Mon, 19 Mar 2007 16:53:29 -0700
Would it provide a superior solution if we were to a) stop zeroing out the
pte's when doing a fullmm==1 teardown and b) go direct to the page allocator
for these pages?
While you could avoid zero'ing them out, you
On Mon, 19 Mar 2007 16:57:55 -0700 (PDT)
Christoph Lameter [EMAIL PROTECTED] wrote:
On Mon, 19 Mar 2007, Andrew Morton wrote:
Has it been proven that quicklists are superior to simply going direct to
the
page allocator for these pages?
Yes.
Sigh.
Please provide proof that
Hiyas,
at the moment, some file in Documentation are utf-8 encoded and some are
latin1 encoded. Therefore I propose to change the default encoding to utf-8,
because this is the encoding that may current linux distributions use.
I can send a patch, if required. If you want to change the
On 03/19, Davide Libenzi wrote:
+struct signalfd_lockctx {
+ struct task_struct *tsk;
+ struct sighand_struct *sighand;
+ unsigned long flags;
+};
signalfd_lockctx is private to signalfd_lock/signalfd_unlock. But lk-sighand
is used only by signalfd_lock(). I'd suggest to remove
On Tue, 20 Mar 2007, Oleg Nesterov wrote:
On 03/19, Davide Libenzi wrote:
+struct signalfd_lockctx {
+ struct task_struct *tsk;
+ struct sighand_struct *sighand;
+ unsigned long flags;
+};
signalfd_lockctx is private to signalfd_lock/signalfd_unlock. But
lk-sighand
is
On Mon, 19 Mar 2007 15:37:16 -0800 (PST)
Christoph Lameter [EMAIL PROTECTED] wrote:
...
--- /dev/null 1970-01-01 00:00:00.0 +
+++ linux-2.6.21-rc3-mm2/include/linux/quicklist.h2007-03-16
02:19:15.0 -0700
@@ -0,0 +1,95 @@
+#ifndef LINUX_QUICKLIST_H
+#define
On 03/19, Davide Libenzi wrote:
+static void signalfd_unlock(struct signalfd_ctx *ctx,
+ struct signalfd_lockctx *lk)
+{
+ unlock_task_sighand(lk-tsk, lk-flags);
+}
Again, this is a matter of taste. But I can't understand why signalfd_unlock()
needs signalfd_ctx
On Tue, 20 Mar 2007, Oleg Nesterov wrote:
On 03/19, Davide Libenzi wrote:
+static void signalfd_unlock(struct signalfd_ctx *ctx,
+ struct signalfd_lockctx *lk)
+{
+ unlock_task_sighand(lk-tsk, lk-flags);
+}
Again, this is a matter of taste. But I can't
On Wed, 7 Mar 2007 20:19:15 -0800 Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm2/
- This is the same as 2.6.21-rc3-mm1, except Con's CPU scheduler changes
were dropped.
This is for A/B comparison purposes, and because
On Mon, 12 Mar 2007 22:19:20 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
Make swsusp use memory bitmaps instead of page flags for marking 'nosave' and
free pages. This allows us to 'recycle' two page flags that can be used for
other
purposes. Also, the memory needed to store the
On Mon, 2007-03-19 at 17:32 -0500, Matt Mackall wrote:
If a static volume is simply a non-dynamic volume, then device mapper
can do that too. And countless other things. Which is not an aside.
UBI growing to do all the things that device mapper does is exactly
the thing we should be
Davide Libenzi a écrit :
+struct timerfd_ctx {
+ struct hrtimer tmr;
+ ktime_t tintv;
+ spinlock_t lock;
+ wait_queue_head_t wqh;
+ unsigned long ticks;
+};
+static struct kmem_cache *timerfd_ctx_cachep;
+ timerfd_ctx_cachep =
On Mon, 2007-03-19 at 16:36 -0500, Matt Mackall wrote:
On Mon, Mar 19, 2007 at 11:06:33PM +0200, Artem Bityutskiy wrote:
On Mon, 2007-03-19 at 14:54 -0500, Matt Mackall wrote:
The issue is 14000 lines of patch to make a parallel subsystem.
Parallel system exists since very long. One is
On Mon, 19 Mar 2007 17:27:11 -0700
Randy Dunlap [EMAIL PROTECTED] wrote:
On Wed, 7 Mar 2007 20:19:15 -0800 Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm2/
- This is the same as 2.6.21-rc3-mm1, except Con's CPU scheduler
Tasos Parisinos [EMAIL PROTECTED] :
[...]
RSA is slow. syscalls are fast.
Which part of the kernel is supposed to benefit from this code ?
--
Ueimor
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, 19 Mar 2007, Andrew Morton wrote:
Please provide proof that quicklists are superior to simply going direct to
the page allocator for these pages.
See the patch. We are only touching 2 cachelines instead of 32. So even
without considering the page allocator overhead and the slab
Hello,
can anyone suggest me a proper way how to schedule UDP packets to transmit at
some given rate?
E.g., I have two boxes both having 10 GE interfaces. One box is able to
transmit at 9.9Gbps, the other one is able to receive only at about 5.5Gbps.
Flow control must be turned off for some
On Mon, 19 Mar 2007 17:39:15 -0700 Andrew Morton wrote:
On Mon, 19 Mar 2007 17:27:11 -0700
Randy Dunlap [EMAIL PROTECTED] wrote:
On Wed, 7 Mar 2007 20:19:15 -0800 Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc3/2.6.21-rc3-mm2/
-
Split the anonymous and file backed pages out onto their own pageout
queues. This we do not unnecessarily churn through lots of anonymous
pages when we do not want to swap them out anyway.
This should (with additional tuning) be a great step forward in
scalability, allowing Linux to run well on
On Monday 19 March 2007 22:43:20 you wrote:
Hi,
On Monday, 19 March 2007 13:50, Tobias Doerffel wrote:
Hi,
Suspend to RAM used to work fine on my computer (Intel Core Duo, 1 GB
RAM, Intel 82801G (ICH7-chipset) mainboard, NVIDIA-gfx-card,
tg3-ethernet) up to 2.6.20.3. But no matter
On Mon, 19 Mar 2007 17:44:28 -0700 (PDT)
Christoph Lameter [EMAIL PROTECTED] wrote:
On Mon, 19 Mar 2007, Andrew Morton wrote:
Please provide proof that quicklists are superior to simply going direct to
the page allocator for these pages.
See the patch. We are only touching 2 cachelines
Davide,
On Mon, 2007-03-19 at 16:47 -0700, Davide Libenzi wrote:
This patch add an anonymous inode source, to be used for files that need
and inode only in order to create a file*. We do not care of having an
inode for each file, and we do not even care of having different names in
the
On Wed, 7 Mar 2007 17:23:05 -0500, Dmitry Torokhov [EMAIL PROTECTED] wrote:
It seems that if a process keeps a character device open then other
processes will also be able to get into filp-f_op-open(inode,filp)
in chrdev_open() even after a driver called cdev_del() as part of its
unwind
On Mon, 19 Mar 2007, Andrew Morton wrote:
See the patch. We are only touching 2 cachelines instead of 32. So even
without considering the page allocator overhead and the slab allocator
overhead (which will make the situation even better) its superior.
That's not proof, it is
On Mon, 19 Mar 2007, Andrew Morton wrote:
+
+#ifdef CONFIG_QUICKLIST
+
+#ifndef CONFIG_NR_QUICK
+#define CONFIG_NR_QUICK 1
+#endif
No, please don't define config items like this. Do it in Kconfig.
They can be set up in the arch specific Kconfig. Ok. I moved the
#ifndef .. #endif
Rik van Riel wrote:
Split the anonymous and file backed pages out onto their own pageout
queues. This we do not unnecessarily churn through lots of anonymous
pages when we do not want to swap them out anyway.
Please take this patch for a spin and let me know what goes well
and what goes
On Mon, 2007-03-19 at 22:51 +0100, Stefan Prechtel wrote:
2007/3/19, Thomas Gleixner [EMAIL PROTECTED]:
On Mon, 2007-03-19 at 21:35 +0100, Stefan Prechtel wrote:
CPU0 CPU1
0: 28289 0 local-APIC-edge-fasteio timer
...
LOC: 28237 28236
On Tue, Mar 20, 2007 at 01:42:46AM +0100, Thomas Gleixner wrote:
On Mon, 2007-03-19 at 17:32 -0500, Matt Mackall wrote:
If a static volume is simply a non-dynamic volume, then device mapper
can do that too. And countless other things. Which is not an aside.
UBI growing to do all the
On Mon, 19 Mar 2007 18:03:54 -0700 (PDT) Christoph Lameter [EMAIL PROTECTED]
wrote:
On Mon, 19 Mar 2007, Andrew Morton wrote:
See the patch. We are only touching 2 cachelines instead of 32. So even
without considering the page allocator overhead and the slab allocator
overhead
On Tue, 20 Mar 2007, Eric Dumazet wrote:
Davide Libenzi a écrit :
+struct timerfd_ctx {
+ struct hrtimer tmr;
+ ktime_t tintv;
+ spinlock_t lock;
+ wait_queue_head_t wqh;
+ unsigned long ticks;
+};
+static struct kmem_cache *timerfd_ctx_cachep;
+
On Tue, 20 Mar 2007, Thomas Gleixner wrote:
+ error = -ENFILE;
+ file = get_empty_filp();
+ if (!file)
+ goto eexit_1;
make this return -ENFILE; please
Done
+ inode = aino_getinode();
+ if (IS_ERR(inode)) {
+ error = PTR_ERR(inode);
+
Jiri wrote:
Looks like it's related to some change in drivers/ide. As there have been
only 13 patches in this area between rc2 and rc3, it should take only 3 or
4 reboots to figure the offending patch using git-bisect - could you
please give it a try?
I applied all of the 2.6.21-rc2-rc3
On Mon, 19 Mar 2007 22:37:46 +0100 Michal Piotrowski [EMAIL PROTECTED]
wrote:
On 19/03/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Mon, 19 Mar 2007 20:23:40 +0100
Michal Piotrowski [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] napisał(a):
The mm snapshot
On Mon, 19 Mar 2007 17:58:52 -0800 Andrew Morton [EMAIL PROTECTED] wrote:
The kernel without Nick's patchset but with the assert runs OK too. Under
the principle of mm-has-been-too-flakey-lately, I'll drop the patches:
mm-debug-check-for-the-fault-vs-invalidate-race.patch
On Wed, 2007-03-14 at 16:33 -0700, Siddha, Suresh B wrote:
On Tue, Mar 13, 2007 at 05:08:59AM -0700, Nick Piggin wrote:
I would agree that it points to MySQL scalability issues, however the
fact that such large gains come from tcmalloc is still interesting.
What glibc version are you,
can anyone suggest me a proper way how to schedule UDP packets to
transmit at
some given rate?
E.g., I have two boxes both having 10 GE interfaces. One box is able to
transmit at 9.9Gbps, the other one is able to receive only at
about 5.5Gbps.
Flow control must be turned off for some
Just trying to generate an example bounce so Intel can fix
their attachment email filters, ignore me.
#!/bin/sh
#
# Usage: git suck path-to-tree
#
# Pull all patches relative to 'origin' from the tree specified
# and apply them to the current directory tree, keeping all changelog
# and
Andrew Morton wrote:
On Mon, 19 Mar 2007 17:58:52 -0800 Andrew Morton [EMAIL PROTECTED] wrote:
The kernel without Nick's patchset but with the assert runs OK too. Under
the principle of mm-has-been-too-flakey-lately, I'll drop the patches:
On Mon, 19 Mar 2007, Xavier Bestel wrote:
Stock scheduler wins easily, no contest.
What happens when you renice X ?
Dunno -- not necessary with the stock scheduler.
Could you try something like renice -10 $(pidof Xorg) ?
Could you try something as simple and accepting that
On Monday 19 March 2007, James Bottomley wrote:
On Mon, 2007-03-19 at 17:47 -0400, Gene Heskett wrote:
James, could this also be the cause of a tar based backup going crazy
and thinking all data is new under any 2.6.21-rc* kernel I've tested
so far with amanda, which in my case uses tar? I've
This adds an optional wrapper around ata_ac_issue_prot that triggers the LED
layer.
I plan to use this by allowing PMU LED control on G5 towers. My test platform
is a PowerMac 7,3 (Dual G5 2.0GHz, June 2004) with a K2 (sata_svw) controller.
Respin of an earlier patch, based on comments by Tejun
This hooks up ata_ac_issue_prot_with_ledtrigger.
Respin of an earlier patch, based on comments by Tejun Heo Alan Cox.
Signed-off-by: Tony Vroon [EMAIL PROTECTED]
--- linux-2.6/include/linux/libata.h.orig 2007-03-19 21:15:04.0
+
+++ linux-2.6/include/linux/libata.h
The first user of ata_ac_issue_prot_with_ledtrigger, the ServerWorks Frodo/
Apple K2 driver. Used by the IDE LED trigger on G5 towers.
Respin of an earlier patch, based on comments by Tejun Heo Alan Cox.
Signed-off-by: Tony Vroon [EMAIL PROTECTED]
--- linux-2.6/drivers/ata/sata_svw.c.orig
On Tue, 20 Mar 2007 00:25:02 +0100
Andreas Steinmetz [EMAIL PROTECTED] wrote:
Mike Christie wrote:
Mike Christie wrote:
James Bottomley wrote:
On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
I can't even say if the tapes are written correctly as I can't read them
(one does not
Andrew Morton wrote:
On Tue, 20 Mar 2007 00:25:02 +0100
Andreas Steinmetz [EMAIL PROTECTED] wrote:
Mike Christie wrote:
Mike Christie wrote:
James Bottomley wrote:
On Mon, 2007-03-19 at 12:49 -0500, Mike Christie wrote:
I can't even say if the tapes are written correctly as I can't read
On 3/15/07, Éric Piel [EMAIL PROTECTED] wrote:
03/14/2007 08:02 PM, Vojtech Pavlik wrote/a écrit:
On Wed, Mar 14, 2007 at 02:58:49PM -0400, Dmitry Torokhov wrote:
2. I also have a concern about using KEY_SCREEN to signal toggling
display on and off. I am CCing Vojtech - he must know what the
19.03.2007 22:28, Dmitry Torokhov wrote/a écrit:
On 3/15/07, Éric Piel [EMAIL PROTECTED] wrote:
Ok, so let me summarize:
There are two kinds of keys on those laptops (for which we are not sure
about the keycode that it should generate):
* Laptop screen on/off
* Display output selection (for
On Saturday, March 17, 2007 2:33 PM, James W. Laferriere wrote:
Hello All , I am have been having this problem since I
purchased the
controller and after changing out the disks I thought were
the problem .
I am still getting the continous :
mptscsih: ioc1: attempting task
On Mon, 2007-03-19 at 13:21 +0300, Alexey Dobriyan wrote:
I very much agree with proto-patch which _copies_ all relevant
information into caller-supplied structure, keeping module_mutex private.
Time to split it sanely.
Indeed. The current interface needs to be ripped apart and put together
On Mon, 2007-03-19 at 17:33 +0300, Alexey Dobriyan wrote:
Iterating code of /proc/kallsyms calls module_get_kallsym() which grabs
and drops module_mutex internally and returns struct module *,
module is removed, aforementioned struct module * is used in non-trivial
way.
Hi Alexey,
I
Alan Cox [EMAIL PROTECTED] wrote:
IMHO the problem with classifying RxRPC as a reliable datagram
socket is that even an atomic unidirectional communication isn't a
single datagram, it's at least 3; there is shared connection state
Thats fine. Any *reliable* protocol sends more than
message transmission. You yourself defined RDM to be a datagram service.
RxRPC is not, in my opinion, a datagram service, and neither is it a stream
service.
Message is what I should have said.
Interestingly, searching for SOCK_RDM definitions with google shows there's
some disagreement as
Alan Cox [EMAIL PROTECTED] wrote:
message transmission. You yourself defined RDM to be a datagram service.
RxRPC is not, in my opinion, a datagram service, and neither is it a stream
service.
Message is what I should have said.
socket(2) also says datagram...
Which is just fine, does
Other RPC types use normal socket types.
They do? Examples please. I didn't think Linux, at least, has any other RPC
socket families, though I could be wrong as I haven't made a thorough study of
them.
SunRPC is implemented in user space and uses the existing TCP/IP layer
and socket
Alan Cox [EMAIL PROTECTED] wrote:
Other RPC types use normal socket types.
They do? Examples please. I didn't think Linux, at least, has any other
RPC socket families, though I could be wrong as I haven't made a thorough
study of them.
SunRPC is implemented in user space and uses
O No, it's not. SOCK_DGRAM is an unreliable, unidirectional datagram passing
service.
Thats funny UDP receives and sends packets.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Sat, Mar 17, 2007 at 10:08:10PM +0900, takada wrote:
I tested some patterns. just X86_OOSTORE was effective. WBINVD is needless.
--- arch/i386/Kconfig.cpu~2007-02-05 03:44:54.0 +0900
+++ arch/i386/Kconfig.cpu 2007-02-17 21:25:52.0 +0900
@@ -322,7 +322,7 @@ config
Rusty Russell [EMAIL PROTECTED] writes:
On Sun, 2007-03-18 at 13:08 +0100, Andi Kleen wrote:
The idea is _NOT_ that you go look for references to the paravirt_ops
members structure, that would be stupid and you wouldn't be able to
use the most efficient addressing mode on a given cpu,
On Mon, 19 Mar 2007, Eric W. Biederman wrote:
True. You can use all of the call clobbered registers.
Quite often, the biggest single win of inlining is not so much the code
size (although if done right, that will be smaller too), but the fact that
inlining DOES NOT CLOBBER AS MANY
* Eric W. Biederman ([EMAIL PROTECTED]) wrote:
Is it truly critical to inline any of these instructions?
I don't have any current measurements. But we'd been aiming
at getting irq_{en,dis}able to a simple memory write to pda.
But simplicity, maintenance, etc. win over trimming a couple
cycles,
801 - 900 of 965 matches
Mail list logo
