__GFP_MEMALLOC will allow the allocation to disregard the watermarks,
much like PF_MEMALLOC.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
include/linux/gfp.h |3 ++-
mm/page_alloc.c |4 +++-
2 files changed, 5 insertions(+), 2 deletions(-)
Index:
Introduce sk_allocation(), this function allows to inject sock specific
flags to each sock related allocation.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
include/net/sock.h|5 +
net/ipv4/tcp.c|2 +-
net/ipv4/tcp_output.c | 11 ++-
net/ipv6/tcp_ipv6.c
Wrap calling sk->sk_backlog_rcv() in a function. This will allow extending the
generic sk_backlog_rcv behaviour.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
include/net/sock.h |5 +
net/core/sock.c |4 ++--
net/ipv4/tcp.c |2 +-
net/ipv4/tcp_timer.c |2
Provide a method to get the upper bound on the pages needed to allocate
a given number of objects from a given kmem_cache.
This lays the foundation for a generic reserve framework as presented in
a later patch in this series. This framework needs to convert object demand
(kmalloc() bytes,
Change ALLOC_NO_WATERMARK page allocation such that the reserves are system
wide - which they are per setup_per_zone_pages_min(), when we scrape the
barrel, do it properly.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
mm/page_alloc.c |6 ++
1 file changed, 6 insertions(+)
Allow PF_MEMALLOC to be set in softirq context. When running softirqs from
a borrowed context save current->flags, ksoftirqd will have its own
task_struct.
This is needed to allow network softirq packet processing to make use of
PF_MEMALLOC.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
Do as Trond suggested:
http://lkml.org/lkml/2006/8/25/348
Disable NFS data cache revalidation on swap files since it doesn't really
make sense to have other clients change the file while you are using it.
Thereby we can stop setting PG_private on swap pages, since there ought to
be no further
Failing to allocate a cache entry will only harm performance not correctness.
Do not consume valuable reserve pages for something like that.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
Acked-by: James Morris <[EMAIL PROTECTED]>
---
security/selinux/avc.c |2 +-
1 file changed, 1
It could happen that all !SOCK_MEMALLOC sockets have buffered so much data
that we're over the global rmem limit. This will prevent SOCK_MEMALLOC buffers
from receiving data, which will prevent userspace from running, which is needed
to reduce the buffered data.
Fix this by exempting the
Change the skb allocation api to indicate RX usage and use this to fall back to
the reserve when needed. SKBs allocated from the reserve are tagged in
skb->emergency.
Teach all other skb ops about emergency skbs and the reserve accounting.
Use the (new) packet split API to allocate and track
Add reserves for INET.
The two big users seem to be the route cache and ip-fragment cache.
Reserve the route cache under generic RX reserve, its usage is bounded by
the high reclaim watermark, and thus does not need further accounting.
Reserve the ip-fragement caches under SKB data reserve,
Restrict objects from reserve slabs (ALLOC_NO_WATERMARKS) to allocation
contexts that are entitled to it. This is done to ensure reserve pages don't
leak out and get consumed.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
include/linux/slub_def.h |1
mm/slab.c| 59
Provide the basic infrastructure to reserve and charge/account network memory.
We provide the following reserve tree:
1) total network reserve
2)network TX reserve
3) protocol TX pages
4)network RX reserve
5) SKB data reserve
[1] is used to make all the network reserves a
In order to teach filesystems to handle swap cache pages, two new page
functions are introduced:
pgoff_t page_file_index(struct page *);
struct address_space *page_file_mapping(struct page *);
page_file_index - gives the offset of this page in the file in PAGE_CACHE_SIZE
blocks. Like
In order to make sure emergency packets receive all memory needed to proceed
ensure processing of emergency SKBs happens under PF_MEMALLOC.
Use the (new) sk_backlog_rcv() wrapper to ensure this for backlog processing.
Skip taps, since those are user-space again.
Signed-off-by: Peter Zijlstra
GFP_NOFS is not enough, since swap traffic is IO, hence fall back to GFP_NOIO.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
fs/nfs/pagelist.c |2 +-
fs/nfs/write.c|6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
Index: linux-2.6/fs/nfs/write.c
From: "guanxun mu" <[EMAIL PROTECTED]>
Date: Fri, 14 Dec 2007 14:03:05 +0800
> [PACTH APPLETALK]
>
> This patch update proto_init process when register_snap_client failed
>
> Signed-off-by: Michale Moore <[EMAIL PROTECTED]>
>
> diff --git a/net/appletalk/aarp.c b/net/appletalk/aarp.c
> index
Move around the swap entry methods in preparation for use from
page methods.
Also provide a function to obtain the swap_info_struct backing
a swap cache page.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
include/linux/mm.h |8 +++
include/linux/swap.h| 49
Generic reserve management code.
It provides methods to reserve and charge. Upon this, generic alloc/free style
reserve pools could be build, which could fully replace mempool_t
functionality.
It should also allow for a Banker's algorithm replacement of __GFP_NOFAIL.
Signed-off-by: Peter
Toss all emergency packets not for a SOCK_MEMALLOC socket. This ensures our
precious memory reserve doesn't get stuck waiting for user-space.
The correctness of this approach relies on the fact that networks must be
assumed lossy.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
New addres_space_operations methods are added:
int swapfile(struct address_space *, int);
int swap_out(struct file *, struct page *, struct writeback_control *);
int swap_in(struct file *, struct page *);
When during sys_swapon() the swapfile() method is found and returns no error
the
Replace all relevant occurences of page->index and page->mapping in the NFS
client with the new page_file_index() and page_file_mapping() functions.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
fs/nfs/file.c |8
fs/nfs/internal.h |7 ---
fs/nfs/pagelist.c |6
With the introduction of the shared dirty page accounting in .19, NFS should
not be able to surpise the VM with all dirty pages. Thus it should always be
able to free some memory. Hence no more need for mempools.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
fs/nfs/read.c | 15
Implement all the new swapfile a_ops for NFS. This will set the NFS socket to
SOCK_MEMALLOC and run socket reconnect under PF_MEMALLOC as well as reset
SOCK_MEMALLOC before engaging the protocol ->connect() method.
PF_MEMALLOC should allow the allocation of struct socket and related objects
and
Provide means to reserve a specific amount of pages.
The emergency pool is separated from the min watermark because ALLOC_HARDER
and ALLOC_HIGH modify the watermark in a relative way and thus do not ensure
a strict minimum.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
Factor out the gfp to alloc_flags mapping so it can be used in other places.
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
mm/internal.h | 11 ++
mm/page_alloc.c | 98
2 files changed, 67 insertions(+), 42 deletions(-)
Hi,
Another posting of the full swap over NFS series.
Andrew/Linus, could we start thinking of sticking this in -mm?
[ patches against 2.6.24-rc5-mm1, also to be found online at:
http://programming.kicks-ass.net/kernel-patches/vm_deadlock/v2.6.24-rc5-mm1/ ]
The patch-set can be split in
Avoid memory getting stuck waiting for userspace, drop all emergency packets.
This of course requires the regular storage route to not include an NF_QUEUE
target ;-)
Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
---
net/netfilter/core.c |3 +++
1 file changed, 3 insertions(+)
Index:
Stephane Eranian <[EMAIL PROTECTED]> writes:
> [...] AFAIK, there is no single call to stop T1 and wait until it
> is completely off the CPU, unless we go through the (internal)
> ptrace interface.
The utrace code supports this style of thread manipulation better
than ptrace.
- FChE
--
To
> If anyone has a testcase - I can take a look at the problem again.
I can try and throw something together..
- z
--
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 Fri, Dec 14, 2007 at 11:00:35AM -0800, Joe Perches wrote:
> Makes an embedded image a bit smaller
Looks good to me. This should probably go to Andrew first though. And
it wouldn't hurt to see some size(1) results.
Acked-by: Matt Mackall <[EMAIL PROTECTED]>
>
> Signed-off-by: Joe Perches
On Friday 14 December 2007 19:45:02 Ray Lee wrote:
> > > One problem related to b43 source code, patch exists, has yet to be
> > > merged upstream.
> >
> > Yeah. A problem preventing a LED from blinking.
> > That's a real regression Come on. Stop that bullshit.
>
> I'm going to say this one
Thomas Gleixner wrote:
The problem is caused by an SMI during the calibration routine. We
really need to come up with a solid solution which does not rely on
the periodic timer coming in, when there is something else (HPET,
pm_timer) available.
I have a look into this.
Arun, do you have an
Makes an embedded image a bit smaller
Signed-off-by: Joe Perches <[EMAIL PROTECTED]>
---
include/linux/kernel.h | 20 +++-
kernel/printk.c|2 ++
kernel/sysctl.c| 20 ++--
3 files changed, 27 insertions(+), 15 deletions(-)
diff --git
H. Peter Anvin wrote:
Greg KH wrote:
But it ignored the fact that I said I didn't want this binary file in
sysfs :)
Please take Eric's suggestion and split it up into the different pieces.
Some of the fields can be binary files, as they come directly from the
firmware, but the others should
On Tue, 2007-12-11 at 17:00 -0800, Zach Brown wrote:
> Hisashi Hifumi wrote:
> > Hi.
> >
> > Current dio has some problems:
> > 1, In ext3 ordered, dio write can return with EIO because of the race
> > between invalidation of
> > a page and jbd. jbd pins the bhs while committing journal so
> >
On Fri, Dec 14, 2007 at 09:58:40AM -0800, Andrew Morton wrote:
> arch/um/include/um_uaccess.h already includes fixmap.h. Is this a -mm-only
> fix?
Whoops, it is. The include was removed by uml-header-untangling.patch,
so folding this into that would work.
Jeff
On Fri, Dec 14, 2007 at 10:46:36AM -0800, Arjan van de Ven wrote:
> The http://www.kerneloops.org website collects kernel oops and warning
> reports from various mailing lists and bugzillas; below is a top 10
> list of the oopses collected in the last 7 days. (Reports prior to 2.6.23
> have
Remove duplicated headers in drivers/parisc/ccio-dma.c:
drivers/parisc/ccio-dma.c: linux/proc_fs.h is included more than once.
Signed-off-by: Francisco Alecrim <[EMAIL PROTECTED]>
---
drivers/parisc/ccio-dma.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
Remove duplicated headers in drivers/input:
drivers/input/keyboard/bf54x-keys.c: linux/irq.h is included more than once.
drivers/input/keyboard/jornada720_kbd.c: linux/init.h is included more than
once.
drivers/input/gameport/gameport.c: linux/sched.h is included more than once.
Signed-off-by:
Remove duplicated headers in drivers/misc/atmel-ssc.c:
drivers/misc/atmel-ssc.c: linux/list.h is included more than once.
Signed-off-by: Francisco Alecrim <[EMAIL PROTECTED]>
---
drivers/misc/atmel-ssc.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
Hi all,
The series of 6 patches contain clean ups related to duplicated headers.
Regards,
Alecrim.
--
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
Remove duplicated headers in drivers/char/keyboard.c:
drivers/char/keyboard.c: linux/consolemap.h is included more than once.
Signed-off-by: Francisco Alecrim <[EMAIL PROTECTED]>
---
drivers/char/keyboard.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
Remove duplicated headers in drivers/net:
drivers/net/ucc_geth_ethtool.c: asm/uaccess.h is included more than once.
drivers/net/irda/ks959-sir.c: linux/module.h is included more than once.
drivers/net/irda/ksdazzle-sir.c: linux/module.h is included more than once.
Signed-off-by: Francisco Alecrim
Remove duplicated headers in SPI subsystem:
drivers/spi/spi_butterfly.c: linux/spi/spi_bitbang.h is included more than once.
drivers/spi/spi_lm70llp.c: linux/spi/spi_bitbang.h is included more than once.
drivers/spi/spi_s3c24xx_gpio.c: linux/spi/spi_bitbang.h is included more than
once.
Hi all,
The series of 6 patches contain clean ups related to duplicated headers.
Regards,
Alecrim.
--
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
Alan Cox wrote:
i dont think this should matter: old systems that truly _need_ the ISA
delay will be slow enough to not trip up. (nor are they really affected
by these early delays - the delays were more for crappy ISA devices that
get initialized later down, when the delay loop is already
The http://www.kerneloops.org website collects kernel oops and warning reports from various mailing lists and bugzillas; below is a top 10
list of the oopses collected in the last 7 days. (Reports prior to 2.6.23 have been omitted in collecting the top 10)
This is the first such report that I'm
On Dec 14, 2007 10:11 AM, Ingo Molnar <[EMAIL PROTECTED]> wrote:
> * Ray Lee <[EMAIL PROTECTED]> wrote:
>
> > Now I'm going to go off, sit in the sun, sip some coffee, and think
> > happy thoughts of kittens playing with yarn for a while.
>
> ok, and given the time-shift and apparent season-shift
I've run out of time to donate to the kernel today, so I'll keep this short.
On Dec 14, 2007 10:22 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > > If you have a PCI device probing works as follows:
> > > The PCI table is in ssb. So as soon as your kernel detects the PCI device
> > > it will
> > i dont think this should matter: old systems that truly _need_ the ISA
> > delay will be slow enough to not trip up. (nor are they really affected
> > by these early delays - the delays were more for crappy ISA devices that
> > get initialized later down, when the delay loop is already
On Friday 14 December 2007 18:59:10 Ingo Molnar wrote:
>
> * Michael Buesch <[EMAIL PROTECTED]> wrote:
>
> > In my opinion this all is the work of the distributions and not the
> > work of the kernel developers. Distributions have to make sure that
> > everything works after a kernel update.
>
> Odd. I knew the resource allocation stuff has it's issues for some
> non-trivial configuration but that one is a new one. Which makes me
> wonder if your platform runs the PCI code in probe-only mode where it
> will not actually assign resources but only inherit the whole PCI setup
>
On Fri, Dec 14, 2007 at 01:42:12AM +0100, Andi Kleen wrote:
> > +void __cpuinit pat_init(void)
> > +{
> > + /* Set PWT+PCD to Write-Combining. All other bits stay the same */
> > + if (cpu_has_pat) {
>
> All the old CPUs (PPro etc.) with known PAT bugs need to clear this flag
> now in their
Matthew Wilcox wrote:
On Fri, Dec 14, 2007 at 05:42:37PM +, Mel Gorman wrote:
Regrettably this interferes with anti-fragmentation because the "next" page
on the list on return from rmqueue_bulk is not guaranteed to be of the right
mobility type. I fixed it as an additional patch but it adds
On 14-12-07 19:02, H. Peter Anvin wrote:
I believe this will suffer from the issue that was raised: this will use
udelay() long before loop calibration (and no, we can't just "be
conservative" since there is no "conservative" value we can use.)
Worse, I suspect that at least the PIT, which
On Friday 14 December 2007 19:01:51 Ray Lee wrote:
> No, I don't have module autoloading disabled. modprobe-ing b43
> automatically loads ssb. Neither, however, will load rfkill or
> rfkill-input. And if they aren't loaded, then b43/ssb are *completely*
> silent during load. Nothing to dmesg at
> As you can see, the global purge rates can be pretty respectable
> under this kind of load. I chose -j50 to generate enough processes
> to stress my own system, you may need more with 4G. Check with
> xosview or similar that the buffer cache fills up memory but
> is kept relatively small by
On Fri, Dec 14, 2007 at 05:42:37PM +, Mel Gorman wrote:
> Regrettably this interferes with anti-fragmentation because the "next" page
> on the list on return from rmqueue_bulk is not guaranteed to be of the right
> mobility type. I fixed it as an additional patch but it adds additional cost
>
Greg KH wrote:
But it ignored the fact that I said I didn't want this binary file in
sysfs :)
Please take Eric's suggestion and split it up into the different pieces.
Some of the fields can be binary files, as they come directly from the
firmware, but the others should be text.
But PLEASE
> magically in the SMM code. To work around this is we would need to add
> the broadcast notification to the halt(), safe_halt(), pm_idle_halt()
> variants which float around in the kernel and make this conditional on
> the C1E detection. That's nasty, but it seems the only solution for
> now.
On
* Ray Lee <[EMAIL PROTECTED]> wrote:
> Now I'm going to go off, sit in the sun, sip some coffee, and think
> happy thoughts of kittens playing with yarn for a while.
ok, and given the time-shift and apparent season-shift i'll sit in the
evening, watch the snowfall and think happy thoughts of
On Fri, 14 Dec 2007, Eduard-Gabriel Munteanu wrote:
> LAPIC is seemingly disabled (C1E detection code does this), but
> clockevents still tries to use it, instead of relying on HPET.
It relies on HPET. The LAPIC is just used as a mechanism which allows
us to broadcast the tick to both cores.
>
> LAPIC is seemingly disabled (C1E detection code does this), but
It should only disable the LAPIC timer, but not the full use of the
LAPIC.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Eric Dumazet wrote:
> On Tue, 14 Aug 2007 20:00:15 +0200
> Tobias Diedrich <[EMAIL PROTECTED]> wrote:
>
> > Eric Dumazet wrote:
> >
> > > Tobias Diedrich <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hello,
> > > >
> > > > I suspect I'm seeing a slow dst cache leakage on one of my servers.
> > > >
Mel Gorman wrote:
On (13/12/07 19:46), Mark Lord didst pronounce:
"Improved version", more similar to the 2.6.23 code:
Fix page allocator to give better chance of larger contiguous segments
(again).
Signed-off-by: Mark Lord <[EMAIL PROTECTED]
Regrettably this interferes with
Sam Ravnborg wrote:
I understood that bc is unreliable.
How about creating a small .c program that does to necessary computation
and integrate it in the build process.
It should be much cleaner than this approach.
You'd have to include an extended-precision library in said C program.
Ingo Molnar wrote:
wow, cool fix! (I remember that there were other systems as well that
are affected by port 0x80 muckery - i thought we had removed port 0x80
accesses long ago.)
how about the simpler fix below, as a first-level approach? We can then
remove the _p in/out sequences after
On Fri, Dec 14, 2007 at 09:27:55PM +0800, Herbert Xu wrote:
> Hi:
>
> [PATCH] Make WARN_ON/WARN_ON_ONCE no-ops when CONFIG_BUG is off
>
> The description of CONFIG_BUG clearly states that both BUG and
> WARN_ON may be skipped. However, our actual implementation still
> checks the condition on
On Dec 14, 2007 8:49 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> On Friday 14 December 2007 17:06:39 Ray Lee wrote:
> > Hi all. Perhaps I can inject some facts into this?
> >
> > On Dec 14, 2007 5:08 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > > > > This user did get the following
* Michael Buesch <[EMAIL PROTECTED]> wrote:
> In my opinion this all is the work of the distributions and not the
> work of the kernel developers. Distributions have to make sure that
> everything works after a kernel update. [...]
actually, not. The the task of kernel developers is to KEEP
ext4 needs to deal with 2 different max file offsets for block- and
extent-allocated file formats, whereas the s_maxbytes scheme can only deal
with one. So, for block-allocated files, we must catch and fix up
too-large offsets from within the filesystem.
Having iov_shorten exported allows such
On Fri, 14 Dec 2007 11:16:47 -0500 Jeff Dike <[EMAIL PROTECTED]> wrote:
> [ This needs to go into 2.6.24, as it fixes a build breakage seen on x86_64 ]
>
> um_uaccess.h refers to FIXADDR_USER_*, so it should include fixmap.h.
>
> I also changed the non-UML includes to use <> instead of "".
>
>
>From: Olof Johansson [mailto:[EMAIL PROTECTED]
>Sent: Thursday, December 13, 2007 7:32 PM
>To: Haavard Skinnemoen
>Cc: Nelson, Shannon; Williams, Dan J;
>linux-kernel@vger.kernel.org; Sam Ravnborg
>Subject: Re: [PATCH v2] dmaengine: Simple DMA memcpy test client
>
>On Fri, Nov 23, 2007 at
On Fri, 14 Dec 2007 21:46:37 +0530 Dhaval Giani <[EMAIL PROTECTED]> wrote:
> On Sat, Dec 15, 2007 at 12:54:09AM +0900, Tejun Heo wrote:
> > Dhaval Giani wrote:
> > > XXX sysfs_page_cnt=1
> >
> > Hmm.. so, sysfs r/w buffer wasn't the culprit. I'm curious what eats up
> > all your low memory.
We can use ilog2() in fs/namespace.c to compute hash_bits and hash_mask at
compile time, not runtime.
Signed-off-by: Eric Dumazet <[EMAIL PROTECTED]>
diff --git a/fs/namespace.c b/fs/namespace.c
index 0608388..835f14a 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -25,6 +25,7 @@
#include
On Fri, 14 Dec 2007 13:45:48 + Russell King <[EMAIL PROTECTED]> wrote:
> Commit 55395ae72b6e5ae614d28df74158c47454652583 introduced:
>
> `.exit.text' referenced in section `.init.text' of drivers/built-in.o:
> defined in discarded section `.exit.text' of drivers/built-in.o
>
> Never mark
On (13/12/07 19:46), Mark Lord didst pronounce:
>
> "Improved version", more similar to the 2.6.23 code:
>
> Fix page allocator to give better chance of larger contiguous segments
> (again).
>
> Signed-off-by: Mark Lord <[EMAIL PROTECTED]
Regrettably this interferes with anti-fragmentation
I have a hand-crafted bad filesystem image which has corruption:
[EMAIL PROTECTED] ~]# ls mnt/dir
file1 file2 file3 file4 file5
[EMAIL PROTECTED] ~]# ls mnt/dir/file4
ls: cannot access mnt/dir/file4: No such file or directory
[EMAIL PROTECTED] ~]# ls -l mnt/dir
ls: cannot access
I have a hand-crafted bad filesystem image which has corruption:
[EMAIL PROTECTED] ~]# ls mnt/dir
file1 file2 file3 file4 file5
[EMAIL PROTECTED] ~]# ls mnt/dir/file4
ls: cannot access mnt/dir/file4: No such file or directory
[EMAIL PROTECTED] ~]# ls -l mnt/dir
ls: cannot access
We can't use the device in a dev_err() after a kzalloc failure or after the
kfree, so
simplify it to the pdev that was originally passed in.
Cc: Eric Sesterhenn <[EMAIL PROTECTED]>
Signed-off-by: Shannon Nelson <[EMAIL PROTECTED]>
---
drivers/dma/ioat_dma.c |2 +-
1 files changed, 1
Hi Tony,
Thanks for testing this. I just tried the following on a 4-way virtual machine
with 2G of memory running on a 4-way rx5670 host with 14G:
# One window: Fill the buffer cache with some stuff
while true; do find / -type f | xargs cat > /dev/null; done
# Another
On Fri, Dec 14, 2007 at 10:37:39PM +0530, Dhaval Giani wrote:
> On Fri, Dec 14, 2007 at 08:26:42AM -0800, Greg KH wrote:
> > On Thu, Dec 13, 2007 at 09:21:26PM +0100, Ingo Molnar wrote:
> > >
> > > * Kay Sievers <[EMAIL PROTECTED]> wrote:
> > >
> > > > > > > This one also fails to apply properly
On Dec 14, 2007 8:59 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> What if you want to compile your own kernel? Well, then you are on
> your own anyway. You have to track kernel changes anyway.
I'm trying to help you test your code before it goes out to the
unsuspecting masses. Do you think I
Hi,
> -Original Message-
> > > +MODULE_AUTHOR("Ben Gardner <[EMAIL PROTECTED]>");
> >
> > But not you?
>
> I'm not even sure if Ben can be said to be an author of this new
> driver, as there is almost no common code between the old driver and
> the new one.
I agree with Jean here.
Describe the ptrace user API changes for this patch set.
Signed-off-by: Markus Metzger <[EMAIL PROTECTED]>
---
Index: man/man2/ptrace.2
===
--- man.orig/man2/ptrace.2 2007-12-14 13:22:17.%N +0100
+++ man/man2/ptrace.2
On Fri, Dec 14, 2007 at 08:26:42AM -0800, Greg KH wrote:
> On Thu, Dec 13, 2007 at 09:21:26PM +0100, Ingo Molnar wrote:
> >
> > * Kay Sievers <[EMAIL PROTECTED]> wrote:
> >
> > > > > > This one also fails to apply properly at the exact same place
> > > > > > has Ingo's previously posted patch.
Here's the new ptrace BTS API that supports two different overflow handling
mechanisms (wrap-around and buffer-full-signal) to support two different use
cases (debugging and profiling).
It further combines buffer allocation and configuration.
Opens:
- memory rlimit
- overflow signal
What
Hi Pete,
On Thu, 13 Dec 2007 13:59:16 -0800, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
> > > > - end_that_request_first(rq, uptodate, rq->hard_nr_sectors);
> > > > - end_that_request_last(rq, uptodate);
> > > > + if (__blk_end_request(rq, error, blk_rq_bytes(rq)))
> > > > +
Change the ptrace interface to mimick an array from newst to oldest.
Signed-off-by: Markus Metzger <[EMAIL PROTECTED]>
---
Index: linux-2.6-x86/arch/x86/kernel/ptrace.c
===
--- linux-2.6-x86.orig/arch/x86/kernel/ptrace.c 2007-12-10
On Friday 14 December 2007 17:45:52 Ray Lee wrote:
> On Dec 14, 2007 8:27 AM, Ray Lee <[EMAIL PROTECTED]> wrote:
> > On Dec 14, 2007 6:40 AM, <[EMAIL PROTECTED]> wrote:
> > > Agreed. As a b43legacy maintainer, I'd be happy to know if Ingo
> > > suggests other ways to smooth out the transition. I
Replace sched_clock() with jiffies for BTS timestamps.
Signed-off-by: Markus Metzger <[EMAIL PROTECTED]>
---
Index: linux-2.6-x86/arch/x86/kernel/ptrace.c
===
--- linux-2.6-x86.orig/arch/x86/kernel/ptrace.c 2007-12-10 09:47:57.%N
In message <[EMAIL PROTECTED]>, Michael Tokarev writes:
> Erez Zadok wrote:
>
> > --- a/Documentation/filesystems/unionfs/usage.txt
> > +++ b/Documentation/filesystems/unionfs/usage.txt
> []
> > +OPTIONS can be any legal combination one of:
>^
> A small
On Fri, Dec 14, 2007 at 09:38:44AM -0600, Matt Mackall wrote:
> On Thu, Dec 13, 2007 at 08:30:41PM -0500, Dave Jones wrote:
> > #ifndef HAVE_ARCH_BUG
> > #define BUG() do { \
> > - printk("BUG: failure at %s:%d/%s()!\n", __FILE__, __LINE__,
> > __FUNCTION__); \
> > + printk(KERN_ERR
Hello,
For an embedded system, I'm currently evaluating the robustness of ufs2
write support on Linux, and my very first test, with fsx, shows serious
problems.
My test bed is a single CPU PC with a single IDE disk, that boots FreeBSD
6.2 and Ubuntu 7.10. The kernel on Ubuntu is a vanilla
Gidday
Some news:
* man-pages now has an (irregularly updated) blog:
http://linux-man-pages.blogspot.com/
Repeating some old news:
* man-pages now has a website:
http://www.kernel.org/doc/man-pages
The site includes HTML versions of the current set of man-pages.
* The list
On Friday 14 December 2007 17:06:39 Ray Lee wrote:
> Hi all. Perhaps I can inject some facts into this?
>
> On Dec 14, 2007 5:08 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > > > This user did get the following messages in dmesg:
> > > >
> > > > b43err(dev->wl, "Firmware file \"%s\" not found
On Thu, Dec 13, 2007 at 09:21:26PM +0100, Ingo Molnar wrote:
>
> * Kay Sievers <[EMAIL PROTECTED]> wrote:
>
> > > > > This one also fails to apply properly at the exact same place
> > > > > has Ingo's previously posted patch. Would need to backport his
> > > > > one.
> > > >
> > > > It
Remove no longer correct comment.
Signed-off-by: Markus Metzger <[EMAIL PROTECTED]>
---
Index: linux-2.6-x86/arch/x86/kernel/process_64.c
===
--- linux-2.6-x86.orig/arch/x86/kernel/process_64.c 2007-12-14 15:31:37.%N
+0100
+++
On Dec 14, 2007 8:27 AM, Ray Lee <[EMAIL PROTECTED]> wrote:
> On Dec 14, 2007 6:40 AM, <[EMAIL PROTECTED]> wrote:
> > Agreed. As a b43legacy maintainer, I'd be happy to know if Ingo
> > suggests other ways to smooth out the transition. I haven't read
> > proposals yet.
>
> This isn't rocket
201 - 300 of 928 matches
Mail list logo
