On Monday 04 December 2006 17:55, Christoph Lameter wrote:
> Could you generalize the reciprocal thingy so that the division
> can be used from other parts of the kernel as well? It would be useful to
> separately get some cycle counts on a regular division compared with your
> division. If that sh
On Mon, 2006-12-04 at 19:12 +0200, Janne Karhunen wrote:
> > 2) NFS provides persistent storage.
>
> To me this sounds like a chicken and an egg problem. It
> both depends and provides this at the same time :/. But
> hey, if it's supposed to work then OK.
??? Locking depends on persistent stora
Hello,
Please forgive me if this is naive. It seems that you could recompile
your tar and patch commands to use the POSIX_FADVISE(2) feature with the
POSIX_FADV_NOREUSE flags. It seems these would cause the tar and patch
commands to not clutter the page cache at all.
It'd be nice to be abl
ext Pierre Ossman wrote:
Anderson Briglia wrote:
@@ -244,5 +244,13 @@ struct _mmc_csd {
#define SD_BUS_WIDTH_1 0
#define SD_BUS_WIDTH_4 2
+/*
+ * MMC_LOCK_UNLOCK modes
+ */
+#define MMC_LOCK_MODE_ERASE(1<<3)
+#define MMC_LOCK_MODE_UNLOCK(0<<2)
+#define MMC_LOCK_MODE_CLR_PWD
On Mon, 4 Dec 2006, Aucoin wrote:
> > From: Horst H. von Brand [mailto:[EMAIL PROTECTED]
> > That means that there isn't a need for that memory at all (and so they
>
> In the current isolated non-production, not actually bearing a load test
> case yes. But if I can't get it to not swap on an idle
Aucoin <[EMAIL PROTECTED]> wrote:
> From: Horst H. von Brand [mailto:[EMAIL PROTECTED]
> > That means that there isn't a need for that memory at all (and so they
> In the current isolated non-production, not actually bearing a load test
> case yes. But if I can't get it to not swap on an idle syst
As a workaround try this:
echo 2 > /proc/sys/vm/overcommit_memory
echo 0 > /proc/sys/vm/overcommit_ratio
Hopefully someone can fix this intrinsic swap before drop behaviour.
Thanks!
--
Al
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EM
On Sun, 2006-12-03 at 01:16 -0800, Andrew Morton wrote:
> On Sun, 03 Dec 2006 00:50:55 -0500
> Ben Collins <[EMAIL PROTECTED]> wrote:
>
> > Fixes this problem when libphy is compiled as module:
> >
> > WARNING: "current_is_keventd" [drivers/net/phy/libphy.ko] undefined!
> >
> > diff --git a/kernel
On Dec 4, 2006, at 8:26 AM, Chen, Kenneth W wrote:
The access_ok() and negative length check on each iov segment in
function
generic_file_aio_read/write are redundant. They are all already
checked
before calling down to these low level generic functions.
...
So it's not possible to call
On Sun, 2006-12-03 at 13:50 +, Ian Campbell wrote:
> In older kernels arch/i386/kernel/timers/timer_pm.c:verify_pmtmr_rate
> contained a check for sensible PMTMR rate and disabled that clocksource
> if it was found to be out of spec[0]. This check seems to have been lost
> in the transition to
This is 100% reproducible. It hangs exportfs on shutdown.
Dec 4 19:50:13 glotze kernel: BUG: unable to handle kernel NULL pointer
dereference at virtual address 0040
Dec 4 19:50:13 glotze kernel: printing eip:
Dec 4 19:50:13 glotze kernel: c017254a
Dec 4 19:50:13 glotze kernel: *pde = 00
On 64-bit arch like x86_64, struct bio is 104 byte. Since bio slab is
created with SLAB_HWCACHE_ALIGN flag, there are usually spare memory
available at the end of bio. I think we can utilize that memory for
bio_vec allocation. The purpose is not so much on saving memory consumption
for bio_vec,
On Mon, 4 Dec 2006 14:07:47 +
[EMAIL PROTECTED] (Mel Gorman) wrote:
> o copy_strings() and variants are no longer setting the flag as the pages
> are not obviously movable when I took a much closer look.
>
> o The arch function alloc_zeroed_user_highpage() is now called
> __alloc_zeroed_u
On Mon, 4 Dec 2006 08:26:36 -0800
"Chen, Kenneth W" <[EMAIL PROTECTED]> wrote:
> So it's not possible to call down to generic_file_aio_read/write with invalid
> iov segment. Patch proposed to delete these redundant code.
erp, please don't touch that code.
The writev deadlock fixes which went in
Hi all,
New in this version:
- mmc_sysfs.c: "change" and "assign" code merged to avoid code
duplication.
- OMAP specific patch not include on this series.
- mmc_lock_unlock function: now, the host is claimed before
mmc_lock_unlock is called.
- Version according the latest mainline git repository
On Mon, 2006-12-04 at 11:19 -0800, john stultz wrote:
> On Sun, 2006-12-03 at 13:50 +, Ian Campbell wrote:
> > In older kernels arch/i386/kernel/timers/timer_pm.c:verify_pmtmr_rate
> > contained a check for sensible PMTMR rate and disabled that clocksource
> > if it was found to be out of spec[
On Mon, 4 Dec 2006, Andrew Morton wrote:
> My concern is that __GFP_MOVABLE is useful for fragmentation-avoidance, but
> useless for memory hot-unplug. So that if/when hot-unplug comes along
> we'll add more gunk which is a somewhat-superset of the GFP_MOVABLE
> infrastructure, hence we didn't ne
On Mon, 4 Dec 2006 19:18:29 +0100
Eric Dumazet <[EMAIL PROTECTED]> wrote:
> On Monday 04 December 2006 17:55, Christoph Lameter wrote:
> > Could you generalize the reciprocal thingy so that the division
> > can be used from other parts of the kernel as well? It would be useful to
> > separately ge
This is similar stuff to asm-generic/div64.h right? The divide overhead
depends on the platform? Maybe it would better to place it in
asm-generic/div.h and then have platform specific functions?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
This patch vs 2.6.19, based on the not-actually-working-for-me
code lurking in libata-dev.git#promise-sata-pata, makes the PATA
ports on my promise sata card actually work. Since the plan as
checked into git, is to drive the PATA ports as if they were
SATA, we have to teach sata_scr_read() to lie
Zach Brown wrote on Monday, December 04, 2006 11:19 AM
> On Dec 4, 2006, at 8:26 AM, Chen, Kenneth W wrote:
>
> > The access_ok() and negative length check on each iov segment in
> > function
> > generic_file_aio_read/write are redundant. They are all already
> > checked
> > before calling do
On Sun, Dec 03, 2006 at 05:26:03PM +0100, Marcel Holtmann wrote:
> Hi Greg,
>
> > Provide a function device_move() to move a device to a new parent device.
> > Add
> > auxilliary functions kobject_move() and sysfs_move_dir().
> > kobject_move() generates a new uevent of type KOBJ_MOVE, containing
> Maybe we should create another internal generic_file_aio_read/write
> for in-core function? fs/read_write.c and fs/aio.c are not module-able
> and the check is already there. For external module, we can do the
> check and then calls down to the internal one.
Maybe. I'd rather see fewer moving
Andrew Morton wrote on Monday, December 04, 2006 11:36 AM
> On Mon, 4 Dec 2006 08:26:36 -0800
> "Chen, Kenneth W" <[EMAIL PROTECTED]> wrote:
>
> > So it's not possible to call down to generic_file_aio_read/write with
> > invalid
> > iov segment. Patch proposed to delete these redundant code.
>
On Fri, 01 Dec 2006 14:19:15 +0100, Jan Glauber said:
> New s390 machines have hardware support for the generation of pseudo-random
> numbers. This patch implements a simple char driver that exports this numbers
> to user-space. Other possible implementations would have been:
> + for (i = 0; i
ib_ucm_cleanup_events() holds file_mutex while calling ib_destroy_cm_id().
This can deadlock since ib_destroy_cm_id() flushes event handlers, and
ib_ucm_event_handler() needs file_mutex, too. Therefore, drop the
file_mutex during the call to ib_destroy_cm_id().
Signed-off-by: Michael S. Tsirkin <
Hello,
I have released another version of the perfmon new code base packages.
There is no major updates in this version compared to 061127. This is
a convenience release so that people can use plain 2.6.19.
The perfmon2 kernel changes are:
- fix UP exit bug in system-wide mode where the
Wendy Cheng wrote:
Andrew Morton wrote:
On Thu, 30 Nov 2006 11:05:32 -0500
Wendy Cheng <[EMAIL PROTECTED]> wrote:
The idea is, instead of unconditionally dropping every buffer
associated with the particular mount point (that defeats the purpose
of page caching), base kernel exports the
I've just upgraded a i686 dual box from 2.6.18.3 to 2.6.19 on a . (I
had been running ALSA 1.0.13.rc3 and also upgraded to the release for
for library and utility programs). The hda-intel driver had problems
with initializing the mic (e.g., using skype for linux), but played
sound properly. Sinc
Kernel-mode traps on x86_64 can pollute the trap information for a previous
userspace trap for which the signal has not yet been delivered to the process.
do_trap and do_general_protection set task->thread.error_code and .trapno
for kernel traps. If a kernel-mode trap arrives between the arrival
The kvm mmu attempts to cache global translations, however it misses on
global huge page translation (which is what most global pages are).
By caching global huge page translations, boot time of fc5 i386 on i386
is reduced from ~35 seconds to ~24 seconds.
Signed-off-by: Avi Kivity <[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em 04-12-2006 12:57, Avi Kivity escreveu:
> The kvm mmu attempts to cache global translations, however it misses on
> global huge page translation (which is what most global pages are).
>
> By caching global huge page translations, boot time of fc5 i3
Renato S. Yamane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Em 04-12-2006 12:57, Avi Kivity escreveu:
The kvm mmu attempts to cache global translations, however it misses on
global huge page translation (which is what most global pages are).
By caching global huge page translation
Avi Kivity wrote:
Whats wrong? :-(
This patch is for kvm, which lives in the -mm kernel. Apply the
latest -mm patch first.
Oh, and visit http://kvm.sourceforge.net first :)
--
error compiling committee.c: too many arguments to function
-
To unsubscribe from this list: send the line
On Mon, 4 Dec 2006, Maneesh Soni wrote:
> hmm, I guess Greg has to say the final word. The question is either to fail
> the IO (-ENODEV) or fail the file removal (-EBUSY). If we are not going to
> fail the removal then your patch is the way to go.
>
> Greg?
Oliver is right that we cannot allow d
Am Montag, 4. Dezember 2006 17:06 schrieb Alan Stern:
> On Mon, 4 Dec 2006, Maneesh Soni wrote:
>
> > hmm, I guess Greg has to say the final word. The question is either to fail
> > the IO (-ENODEV) or fail the file removal (-EBUSY). If we are not going to
> > fail the removal then your patch is t
On Mon, 4 Dec 2006, Oliver Neukum wrote:
> > Also, Oliver, it looks like the latest version of your patch makes an
> > unnecessary change to sysfs_remove_file().
>
> Code like:
>
> int d(int a, int b)
> {
> return a + b;
> }
>
> int c(int a, int b)
> {
> return d(a, b);
> }
>
> is
Am Montag, 4. Dezember 2006 17:57 schrieb Alan Stern:
> I was referring to sysfs_remove_file(), not sysfs_open_file() -- I agree
> that getting rid of the check_perm() routine is good. But this isn't:
>
> > void sysfs_remove_file(struct kobject * kobj, const struct attribute *
> > attr)
> >
On Mon, Dec 04, 2006 at 06:34:06PM +0530, Maneesh Soni wrote:
> On Mon, Dec 04, 2006 at 07:38:00AM +0100, Oliver Neukum wrote:
> > Am Montag, 4. Dezember 2006 05:43 schrieb Maneesh Soni:
> > > On Fri, Dec 01, 2006 at 11:43:06PM +0100, Oliver Neukum wrote:
> > > > Hi,
> > > >
> > > > Alan Stern has
Implement MMC password force erase, remove password, change password,
unlock card and assign password operations. It uses the sysfs mechanism
to send commands to the MMC subsystem.
Signed-off-by: Carlos Eduardo Aguiar indt.org.br>
Signed-off-by: Anderson Lizardo indt.org.br>
Signed-off-by:
On Mon, 2006-12-04 at 19:40 +, Ian Campbell wrote:
> On Mon, 2006-12-04 at 11:19 -0800, john stultz wrote:
> > On Sun, 2006-12-03 at 13:50 +, Ian Campbell wrote:
> > > In older kernels arch/i386/kernel/timers/timer_pm.c:verify_pmtmr_rate
> > > contained a check for sensible PMTMR rate and d
>> 2) NFS provides persistent storage.
>
>To me this sounds like a chicken and an egg problem. It
>both depends and provides this at the same time :/. But
>hey, if it's supposed to work then OK.
Way 1:
mount -nt tmpfs none /var/lib/nfs;
mount -nt nfs fserve:/tftpboot/linux /mnt;
mount -n --mov
On Mon, Dec 04 2006, Chen, Kenneth W wrote:
> On 64-bit arch like x86_64, struct bio is 104 byte. Since bio slab is
> created with SLAB_HWCACHE_ALIGN flag, there are usually spare memory
> available at the end of bio. I think we can utilize that memory for
> bio_vec allocation. The purpose is no
USB_RTL8150 must select MII to avoid link errors.
Stolen from a patch by Randy Dunlap.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 4 Nov 2006
--- linux-2619-rc3-pv.orig/drivers/usb/net/Kconfig
+++ linux-2619-rc3-pv/drivers/usb/net/Kconfig
@@ -84,6 +84,7
On Mon, 4 Dec 2006, Andrew Morton wrote:
> > The multi zone approach does not work with NUMA. NUMA only supports a
> > single zone for memory policy control etc.
>
> Wot? memory policies are a per-vma thing?
They only apply to "policy_zone" of a node. policy_zone can only take a
single type o
On Mon, 4 Dec 2006 12:47:37 -0700
Erik Andersen <[EMAIL PROTECTED]> wrote:
> This patch vs 2.6.19, based on the not-actually-working-for-me
> code lurking in libata-dev.git#promise-sata-pata, makes the PATA
> ports on my promise sata card actually work. Since the plan as
Nice, this is pretty muc
Implement key retention operations.
Signed-off-by: Carlos Eduardo Aguiar indt.org.br>
Signed-off-by: Anderson Lizardo indt.org.br>
Signed-off-by: Anderson Briglia indt.org.br>
Index: linux-linus-2.6/drivers/mmc/Kconfig
===
---
Security fixes since 2.6.16.32:
- CVE-2006-5751: bridge: fix possible overflow in get_fdb_entries
Patch location:
ftp://ftp.kernel.org/pub/linux/kernel/people/bunk/linux-2.6.16.y/testing/
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
RSS feed of the git tree:
On Monday 04 December 2006 20:21, Trond Myklebust wrote:
> > > 2) NFS provides persistent storage.
> >
> > To me this sounds like a chicken and an egg problem. It
> > both depends and provides this at the same time :/. But
> > hey, if it's supposed to work then OK.
>
> ??? Locking depends on persi
When a card is locked, only commands from the "basic" and "lock card" classes
are accepted. To be able to use the other commands, the card must be unlocked
first.
This patch prevents the device drivers from probing the locked cards. Device
probing must be triggered sometime later to make the car
Implement card lock/unlock operation, using the MMC_LOCK_UNLOCK command.
Signed-off-by: Carlos Eduardo Aguiar indt.org.br>
Signed-off-by: Anderson Lizardo indt.org.br>
Signed-off-by: Anderson Briglia indt.org.br>
Index: linux-linus-2.6/drivers/mmc/mmc.h
On Mon, 4 Dec 2006 11:41:42 -0800 (PST)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> > That depends on how we do hot-unplug, if we do it. I continue to suspect
> > that it'll be done via memory zones: effectively by resurrecting
> > GFP_HIGHMEM. In which case there's little overlap with anti-f
Chen, Kenneth W wrote:
> io_submit_one assigns ki_left = ki_nbytes = iocb->aio_nbytes, then
> calls down to aio_setup_iocb, then to aio_setup_single_vector. In there,
> ki_nbytes is reassigned to the same value it got two call stack above it.
> There is no need to do so.
>
> Signed-off-by: Ken Che
On Monday 04 December 2006 22:03, Jan Engelhardt wrote:
> >> 2) NFS provides persistent storage.
> >
> >To me this sounds like a chicken and an egg problem. It
> >both depends and provides this at the same time :/. But
> >hey, if it's supposed to work then OK.
>
> Way 1:
>
> mount -nt tmpfs none /
Anderson Briglia wrote:
>
> Actually they represent the bits regarding the modes and it is used
> when we
> have to send the LOCK/UNLOCK mode on the command data block, according
> to the MMC Spec.
> If you take a look at mmc_lock_unlock function, we use those modes to
> set the right bit
> when co
On Mon, 4 Dec 2006, Andrew Morton wrote:
On Mon, 4 Dec 2006 14:07:47 +
[EMAIL PROTECTED] (Mel Gorman) wrote:
o copy_strings() and variants are no longer setting the flag as the pages
are not obviously movable when I took a much closer look.
o The arch function alloc_zeroed_user_highpage
head: d916faace3efc0bf19fe9a615a1ab8fa1a24cd93
Here a sequential probe, that boots fine:
"
[cut]
ata_piix :00:1f.1: version 2.00ac6
ACPI: PCI Interrupt :00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
PCI: Setting latency timer of device :00:1f.1 to 64
ata1: PATA max UDMA/133 cmd 0x1F0 ct
Hi,
I'd like to announce a new mailing list that has been just set up.
It is oriented toward anyone who is responsible for, or involved with,
the packing up of the Linux kernel for a distro or other group of users.
The list is located at [EMAIL PROTECTED], and
instructions on how to subscribe to
On Mon, Dec 04 2006, Chen, Kenneth W wrote:
> > [...]
> >
> > Another idea would be to kill SLAB_HWCACHE_ALIGN (it's pretty pointless,
> > I bet), and always alloc sizeof(*bio) + sizeof(*bvl) in one go when a
> > bio is allocated. It doesn't add a lot of overhead even for the case
> > where we do
On Mon, 2006-12-04 at 11:30 -0800, Andrew Morton wrote:
> I'd also like to pin down the situation with lumpy-reclaim versus
> anti-fragmentation. No offence, but I would of course prefer to avoid
> merging the anti-frag patches simply based on their stupendous size. It
> seems to me that lumpy-r
Jens Axboe wrote on Monday, December 04, 2006 12:07 PM
> On Mon, Dec 04 2006, Chen, Kenneth W wrote:
> > On 64-bit arch like x86_64, struct bio is 104 byte. Since bio slab is
> > created with SLAB_HWCACHE_ALIGN flag, there are usually spare memory
> > available at the end of bio. I think we can u
On Mon, 2006-12-04 at 21:03 +0100, Jan Engelhardt wrote:
> >> 2) NFS provides persistent storage.
> >
> >To me this sounds like a chicken and an egg problem. It
> >both depends and provides this at the same time :/. But
> >hey, if it's supposed to work then OK.
>
> Way 1:
>
> mount -nt tmpfs no
Alan wrote:
Switch to pci_get_bus_and_slot because some x86 systems seem to be
handing us a device with dev->bus = NULL. Also don't apply the isa fixup
to revision C6 and later of the chip.
Really we need to work out wtf is handing us pdev->bus = NULL, but firstly
and more importantly we need
Alan wrote:
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
applied
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
Thomas Meyer wrote:
head: d916faace3efc0bf19fe9a615a1ab8fa1a24cd93
Here a sequential probe, that boots fine:
Known problem, unfortunately, for a -great- many drivers.
Please turn off this option until the authors fix it.
Jeff
-
To unsubscribe from this list: send the line "unsubsc
> It's rather large, but for those who want to look at it :
> http://www.jdi-ict.nl/plain/serial-28112006.txt
The same problem, this time with 2.6.19. I've done a show tasks, a show
locks, a show regs, and after that, a sync + reboot :)
Log is at http://www.jdi-ict.nl/plain/serial-04122006.txt
Hi Greg,
> > > Provide a function device_move() to move a device to a new parent device.
> > > Add
> > > auxilliary functions kobject_move() and sysfs_move_dir().
> > > kobject_move() generates a new uevent of type KOBJ_MOVE, containing the
> > > previous path (DEVPATH_OLD) in addition to the usu
On Mon, 4 Dec 2006 12:17:26 -0800 (PST)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> > I suspect you'll have to live with that. I've yet to see a vaguely sane
> > proposal to otherwise prevent unreclaimable, unmoveable kernel allocations
> > from landing in a hot-unpluggable physical memory reg
> From: Jeffrey Hundstad [mailto:[EMAIL PROTECTED]
> POSIX_FADV_NOREUSE flags. It seems these would cause the tar and patch
WI may be naïve as well, but that sounds interesting. Unless someone knows
of an obvious reason this won't work we can make a one-off tar command and
give it a whirl.
-
To
I am asking why need to compile the following modules while I do not
have any SCSI device ?
Modules Loaded
rose netrom mkiss ax25 crc16 mach64 drm nfsd exportfs lockd nfs_acl
sunrpc ipv6 snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
ne2k_pci 8390 snd_pcm_oss snd_mixer_oss snd_ens1371 gamep
On Mon, 2006-12-04 at 22:05 +0200, Janne Karhunen wrote:
> On Monday 04 December 2006 20:21, Trond Myklebust wrote:
>
> > > > 2) NFS provides persistent storage.
> > >
> > > To me this sounds like a chicken and an egg problem. It
> > > both depends and provides this at the same time :/. But
> > >
> From: Tim Schmielau [mailto:[EMAIL PROTECTED]
> I believe your OOM problem is not connected to these observations. There
I don't know what to tell you except oom fires only when the update runs. I
know it's a pitiful datapoint so I'll work on getting more data.
-
To unsubscribe from this list:
On Mon, 4 Dec 2006, Andrew Morton wrote:
> What happens when we need to run reclaim against just a section of a zone?
> Lumpy-reclaim could be used here; perhaps that's Mel's approach too?
Why would we run reclaim against a section of a zone?
> We'd need new infrastructure to perform the
> sect
> From: Horst H. von Brand [mailto:[EMAIL PROTECTED]
> How do you /know/ it won't just be recycled in the production case?
In the production case is when oom fires and kills things. I can only assume
memory is not being freed fast enough otherwise oom wouldn't get so upset.
> That is your ultimat
On Mon, 04 Dec 2006 15:48:04 -0500
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Thomas Meyer wrote:
> > head: d916faace3efc0bf19fe9a615a1ab8fa1a24cd93
> >
> > Here a sequential probe, that boots fine:
>
> Known problem, unfortunately, for a -great- many drivers.
>
> Please turn off this option unti
Thank you Andrew for your comments, here is a new version of the patch that
should take them into account.
Maybe it should be split into two different patches ?
One introducing include/linux/reciprocal_div.h and lib/reciprocal_div.c, one
using them in slab ?
[PATCH] SLAB : use a multiply in
On Mon, 4 Dec 2006 15:25:47 -0600
"Aucoin" <[EMAIL PROTECTED]> wrote:
> > From: Jeffrey Hundstad [mailto:[EMAIL PROTECTED]
> > POSIX_FADV_NOREUSE flags. It seems these would cause the tar and patch
>
> WI may be na__ve as well, but that sounds interesting. Unless someone knows
> of an obvious re
Hi,
On Monday 04 December 2006 16:39, Ingo Molnar wrote:
> there's *always* a way to do such things more cleanly - such as the
> patch below. Could you try to fix it up for 32-bit cycles_t platforms? I
> bet the hackery will be limited to now() and maybe the conversion
> routines, instead of spre
From: Eric Dumazet <[EMAIL PROTECTED]>
Date: Mon, 04 Dec 2006 22:34:29 +0100
> On a 200 MHz sparcv9 machine, the division takes 64 cycles instead of 1 cycle
> for a multiply.
For UltraSPARC I and II (which is what this 200mhz guy probably is),
it's 4 cycle latency for a multiply (32-bit or 64-bit
Bernard Pidoux wrote:
I am asking why need to compile the following modules while I do not
have any SCSI device ?
Because your hardware is driven by a libata based driver. This means it
is a scsi bus driver and thus, requires mod_scsi and the scsi disk
module to access disks on the bus.
-
Hi,
> > In ptrace, when request is PPC_PTRACE_GETREGS, SETREGS, GETFPREGS and
> > SETFPREGS, order of the last two arguments is not correct.
> >
> > General format of ptrace is ptrace (request, pid, addr, data). For the
> > above mentioned request ids in ppc64, if we use ptrace like
> >
> >
* Roman Zippel <[EMAIL PROTECTED]> wrote:
> While I'm not against this patch, but on m68k I prefer a 32bit cycle
> type (however it's called), so it doesn't solve the original problem.
i havent changed the cycles_t type - it's still 32-bit. I agree with you
that we dont want to bloat 32-bit ar
Hello,
[1.] One line summary of the problem:
Kernel oops upon boot, but not always. When it boots ok, then PC's working fine.
[2.] Full description of the problem/report:
Following the release of the 2.6.19 kernel, i installed it and after few
reboots , i caught this oops:
Picture's here : ht
This gave me some really odd compile errors.. Theres
a static inline for this function right above this define
so I just dropped the define.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/spinlock.h |1 -
1 files changed, 1 deletion(-)
Index: linux-2.6.19/include/linux/
On Mon, 4 Dec 2006 13:43:44 -0800 (PST)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Mon, 4 Dec 2006, Andrew Morton wrote:
>
> > What happens when we need to run reclaim against just a section of a zone?
> > Lumpy-reclaim could be used here; perhaps that's Mel's approach too?
>
> Why would
On Mon, 4 Dec 2006 20:34:29 + (GMT)
Mel Gorman <[EMAIL PROTECTED]> wrote:
> > IOW: big-picture where-do-we-go-from-here stuff.
> >
>
> Start with lumpy reclaim,
I had lumpy-reclaim in my todo-queue but it seems to have gone away. I
think I need a lumpy-reclaim resend, please.
> then I'd li
utsname information is shown in the linux banner, which
also is used for /proc/version (which can have different
utsname values inside a uts namespaces). this patch
makes the varying data arguments and changes the string
to a format string, using those arguments.
best,
Herbert
Signed-off-by: Her
David Miller a écrit :
From: Eric Dumazet <[EMAIL PROTECTED]>
Date: Mon, 04 Dec 2006 22:34:29 +0100
On a 200 MHz sparcv9 machine, the division takes 64 cycles instead of 1 cycle
for a multiply.
For UltraSPARC I and II (which is what this 200mhz guy probably is),
it's 4 cycle latency for a mul
On Mon, 04 Dec 2006 16:23:27 + Jan Beulich wrote:
> Now that binutils' ld is able to properly populate .eh_frame_hdr in the
> Linux kernel case, here's a patch to add some functionality to the Dwarf2
> unwinder to actually be able to make use of this (applies on firstfloor
> tree with the prev
On Wed, Nov 29, 2006 at 09:18:04PM +, Russell King wrote:
> Unfortunately, the .../new_id feature does not work with the 8250_pci
> driver.
>
> The reason for this comes down to the way .../new_id is implemented.
> When PCI tries to match a driver to a device, it checks the modules
> static de
On Mon, Dec 04, 2006 at 10:15:03PM +0100, Marcel Holtmann wrote:
> Hi Greg,
>
> > > > Provide a function device_move() to move a device to a new parent
> > > > device. Add
> > > > auxilliary functions kobject_move() and sysfs_move_dir().
> > > > kobject_move() generates a new uevent of type KOBJ_
On Mon, 4 Dec 2006 21:02:06 +0100 Adrian Bunk wrote:
> USB_RTL8150 must select MII to avoid link errors.
>
> Stolen from a patch by Randy Dunlap.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Thanks, Adrian.
David B. may prefer a patch similar to the one that was
merged for USB_NET_MCS783
Alan wrote:
On Mon, 4 Dec 2006 12:47:37 -0700
Erik Andersen <[EMAIL PROTECTED]> wrote:
This patch vs 2.6.19, based on the not-actually-working-for-me
code lurking in libata-dev.git#promise-sata-pata, makes the PATA
ports on my promise sata card actually work. Since the plan as
Nice, this is
I have noticed that scsi_do_req has apparently been obsoleted in 2.6.18
and above. Is scst and target support for FC-AL going to
remain supported and/or merged at some point? If so, what is planned
for scst support for later kernels?
Jeff
-
To unsubscribe from this list: send the line "uns
Bernard Pidoux wrote:
I am asking why need to compile the following modules while I do not
have any SCSI device ?
libata uses SCSI to provide a lot of infrastructure that it would
otherwise have to recreate. Also, using SCSI meant that it
automatically worked in existing installers.
On (04/12/06 14:34), Andrew Morton didst pronounce:
On Mon, 4 Dec 2006 20:34:29 + (GMT)
Mel Gorman <[EMAIL PROTECTED]> wrote:
> > IOW: big-picture where-do-we-go-from-here stuff.
> >
>
> Start with lumpy reclaim,
I had lumpy-reclaim in my todo-queue but it seems to have gone away. I
thin
On Mon, Dec 04, 2006 at 09:08:56AM -0800, Bill Huey wrote:
> On Mon, Dec 04, 2006 at 01:21:29PM +0100, bert hubert wrote:
> > How tightly is your work bound to -rt? Iow, any chance of separating the
> > two? Or should we even want to?
>
> There's other uses for it as well. Think about RCU algorith
On Mon, Dec 04, 2006 at 11:10:01AM +0100, Tobias Oed wrote:
> Tomasz Chmielewski wrote:
>
> > Yes, something's using that drive, be it a program, a module (unlikely),
> > or something that is compiled directly in the kernel (for example,
> > md/raid1).
>
> Since you mention md, dm comes to mind.
to: linux-kernel@vger.kernel.org
cc: [EMAIL PROTECTED]
2006/12/04/18:00 CST
Building modules, stage 2.
Kernel: arch/x86_64/boot/bzImage is ready (#2)
MODPOST 1256 modules
WARNING: "current_is_keventd" [drivers/net/phy/libphy.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules
Am Donnerstag, 30. November 2006 09:33 schrieb Ingo Molnar:
> i have released the 2.6.19-rt1 tree, which can be downloaded from the
Hi Ingo,
here comes a freerunning trace explaining the weirdness I see here.
I tried max_latency tracing first, didn't see anything usefull,
went on with tracing fre
201 - 300 of 423 matches
Mail list logo
