Re: [PATCH 04/22] procfs: drop vmtruncate

Looks good, Reviewed-by: Christoph Hellwig -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 06/22] ocfs2: drop vmtruncate

> if ((attr->ia_valid & ATTR_SIZE) && > attr->ia_size != i_size_read(inode)) { > - status = vmtruncate(inode, attr->ia_size); > + status = inode_newsize_ok(inode, attr->ia_size); > if (status) { > mlog_errno(status); >

Re: [PATCH 07/22] adfs: drop vmtruncate

> @@ -57,8 +57,9 @@ static int adfs_write_begin(struct file *file, struct > address_space *mapping, > &ADFS_I(mapping->host)->mmu_private); > if (unlikely(ret)) { > loff_t isize = mapping->host->i_size; > - if (pos + len > isize) > -

Re: [PATCH 09/22] bfs: drop vmtruncate

> @@ -171,8 +171,9 @@ static int bfs_write_begin(struct file *file, struct > address_space *mapping, > bfs_get_block); > if (unlikely(ret)) { > loff_t isize = mapping->host->i_size; > - if (pos + len > isize) > - vmt

Re: [PATCH 14/22] hostfs: drop vmtruncate

> +++ b/fs/hostfs/hostfs_kern.c > @@ -848,9 +848,11 @@ int hostfs_setattr(struct dentry *dentry, struct iattr > *attr) > attr->ia_size != i_size_read(inode)) { > int error; > > - error = vmtruncate(inode, attr->ia_size); > - if (err) > -

Re: [PATCH 17/22] ncpfs: drop vmtruncate

> if (attr->ia_size != i_size_read(inode)) { > - result = vmtruncate(inode, attr->ia_size); > + result = inode_newsize_ok(inode, attr->ia_size); > if (result) > goto out; > + > +

Re: [PATCH v4 1/6] perf tools: configure tmp path at build time

A system that doesn't have /bin/sh is fundamentally broken. How about just creating it as a symlink in a simple unix compatibility layer for Android. That'd help with /tmp as well. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vg

Re: [PATCH v4 6/6] perf stat: implement --big-num grouping

On Tue, Oct 16, 2012 at 02:33:40AM +0300, Irina Tirdea wrote: > From: Irina Tirdea > > In glibc, printf supports ' to group numbers with thousands' grouping > characters. Bionic does not support ' for printf. > > Implement thousands's grouping for numbers according to locale. > The implementatio

Re: [PATCH 1/4] bdi: Track users that require stable page writes

On Tue, Nov 20, 2012 at 06:00:34PM -0800, Darrick J. Wong wrote: > This creates a per-backing-device counter that tracks the number of users > which > require pages to be held immutable during writeout. Eventually it will be > used > to waive wait_for_page_writeback() if nobody requires stable p

Re: [PATCH 1/9] vfs: Handle O_SYNC AIO DIO in generic code properly

On Mon, Nov 19, 2012 at 11:41:23PM -0800, Darrick J. Wong wrote: > Provide VFS helpers for handling O_SYNC AIO DIO writes. Filesystems wanting > to > use the helpers have to pass DIO_SYNC_WRITES to __blockdev_direct_IO. If the > filesystem doesn't provide its own direct IO end_io handler, the ge

Re: [PATCH 3/9] xfs: factor out everything but the filemap_write_and_wait from xfs_file_fsync

On Mon, Nov 19, 2012 at 11:41:38PM -0800, Darrick J. Wong wrote: > Hi, > > Fsyncing is tricky business, so factor out the bits of the xfs_file_fsync > function that can be used from the I/O post-processing path. Why would we need to skip the filemap_write_and_wait_range call here? If we're doing

Re: [PATCH 1/4] bdi: Track users that require stable page writes

On Wed, Nov 21, 2012 at 02:54:35AM -0500, Christoph Hellwig wrote: > On Tue, Nov 20, 2012 at 06:00:34PM -0800, Darrick J. Wong wrote: > > This creates a per-backing-device counter that tracks the number of users > > which > > require pages to be held immutable during writeout

Re: [PATCH 1/4] bdi: Track users that require stable page writes

> +static inline void bdi_require_stable_pages(struct backing_dev_info *bdi) > +{ > + bdi->capabilities |= BDI_CAP_STABLE_WRITES; > +} > + > +static inline void bdi_unrequire_stable_pages(struct backing_dev_info *bdi) > +{ > + bdi->capabilities &= ~BDI_CAP_STABLE_WRITES; > +} Any reason to

Re: [PATCH 2/4] mm: Only enforce stable page writes if the backing device requires it

On Tue, Nov 20, 2012 at 06:00:41PM -0800, Darrick J. Wong wrote: > Create a helper function to check if a backing device requires stable page > writes and, if so, performs the necessary wait. Then, make it so that all > points in the memory manager that handle making pages writable use the helper

Re: [PATCH 1/9] vfs: Handle O_SYNC AIO DIO in generic code properly

On Wed, Nov 21, 2012 at 11:58:05AM -0500, Jeff Moyer wrote: > > I'd like to use this as a vehicle to revisit how dio completions work. > > I don't like the sound of that. ;-) It sounds like this bugfix may get > further delayed by the desire for unrelated code cleanup. I've got a prototype that

Re: [PATCH v4 00/31] loop: Issue O_DIRECT aio using bio_vec

On Wed, Nov 21, 2012 at 04:40:40PM -0600, Dave Kleikamp wrote: > It introduces new file ops, read_iter() and write_iter(), that replace the > aio_read() and aio_write() operations. The iov_iter structure can now contain > either a user-space iovec or a kernel-space bio_vec. Since it would be > over

Re: [PATCH] bdi: Track users that require stable page writes

On Wed, Nov 21, 2012 at 06:33:43PM -0800, Darrick J. Wong wrote: > How's this look to everyone? No more user-writable flag, and most of the > helper functions are gone. Now fix up the subject line as well and we might have a deal :) > (Are these emails even getting through?) At least this one i

Re: [PATCH v4 01/31] iov_iter: move into its own file

On Wed, Nov 21, 2012 at 04:40:41PM -0600, Dave Kleikamp wrote: > From: Zach Brown > > This moves the iov_iter functions in to their own file. We're going to > be working on them in upcoming patches. They become sufficiently large, > and remain self-contained, to justify seperating them from the

Re: [PATCH v4 09/31] dio: create a dio_aligned() helper function

On Wed, Nov 21, 2012 at 04:40:49PM -0600, Dave Kleikamp wrote: > From: Zach Brown > > __blockdev_direct_IO() had two instances of the same code to determine > if a given offset wasn't aligned first to the inode's blkbits and then > to the underlying device's blkbits. This was confusing enough b

Re: [PATCH v4 23/31] nfs: simplify swap

On Wed, Nov 21, 2012 at 04:41:03PM -0600, Dave Kleikamp wrote: > swap_writepage can now call nfs's write_iter f_op, eliminating the need to > implement for the special-case direct_IO a_op. There is no longer a need to > pass the uio flag through the direct write path. This should also kill off the

Re: [PATCH] uprobes: Add exports for module use

On Thu, Jan 10, 2013 at 03:01:46PM -0800, Josh Stone wrote: > The original pull message for uprobes (commit 654443e2) noted: > > This tree includes uprobes support in 'perf probe' - but SystemTap > (and other tools) can take advantage of user probe points as well. > > In order to actually be

Re: [PATCH 1/6] target/file: Re-enable optional fd_buffered_io=1 operation

On Sun, Sep 30, 2012 at 05:58:11AM +, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger > > This patch re-adds the ability to optionally run in buffered FILEIO mode > (eg: w/o O_DSYNC) for device backends in order to once again use the > Linux buffered cache as a write-back storage mech

linux 3.6 compile error in samples/seccomp/bpf-helper.c

Seems like the seccomp example somehow expect linux/seccomp.h to be installed instead of grabbing it from the kernel tree: /home/hch/work/linux-2.6/samples/seccomp/bpf-direct.c:21:27: fatal error: linux/seccomp.h: No such file or directory compilation terminated. /home/hch/work/linux-2.6/samples/

Re: [PATCH 00/16] (Resend) Use get_personality()

On Sat, Feb 23, 2008 at 12:27:10PM +0300, Alexey Dobriyan wrote: > > Use get_personality() can hide the task_struct internals a bit. > > ->personality is going to become something less trivial? > Sorry, but you sound like C++ people writing tons of pointless get/set > wrappers. And your get_person

Re: [PATCH] Use userland-like functions for reading the ACPI table

On Sat, Feb 23, 2008 at 12:45:38PM -0800, Linus Torvalds wrote: > > > > As recommended by Christoph Hellwig, even if we can't rely on the userspace > > firmware loader so early at boot, at least use normal syscall (as in > > init/do_mounts_*.c). Similarly, use

Re: [patch 1/2] x86,fpu: split FPU state from task struct

On Sat, Feb 23, 2008 at 06:34:38PM -0800, Suresh Siddha wrote: > Split the FPU save area from the task struct. This allows easy migration > of FPU context, and it's generally cleaner. It also allows the following > two optimizations: > > 1) only allocate when the application actually uses FPU, so

Re: [patch 2/2] x86,fpu: lazy allocation of FPU area

On Sat, Feb 23, 2008 at 06:34:39PM -0800, Suresh Siddha wrote: > + if (!tsk->thread.cntxt) > +tsk->thread.cntxt = alloc_cntxt_struct(); Please use tabs, not spaces for indentation. > +union thread_cntxt *alloc_cntxt_struct(void) > +{ > + return kmem_cache_alloc(task_cntxt_

Re: [PATCH 1/1] [SCSI] gdth: misc cleanups, preparation for ISA/EISA hotplug API

On Sat, Feb 23, 2008 at 11:44:44PM -0500, Jeff Garzik wrote: > Several misc. cleanups: > > - remove recently-noop'd 'reverse_scan' module parm > > - remove pointless function prototypes > > - remove ha->pccb, its value always == &ha->cmdext > > - move thrice-redundant DMA memory alloc and (in E

Re: [PATCH 1/1] [SCSI] gdth: misc cleanups, preparation for ISA/EISA hotplug API

On Sun, Feb 24, 2008 at 12:18:23AM -0500, Jeff Garzik wrote: > hm. We'll see how it plays out... on the remove side, the above is > exact what happens in gdth_remove_one() without my patch, thus > consolidating two cases of the same code into one. There is a less-strong > argument for doi

Re: [RFC] mmiotrace full patch, preview 1

On Mon, Feb 25, 2008 at 02:49:22PM -0800, Andrew Morton wrote: > the things which it finds. > > > +static DECLARE_MUTEX(kmmio_init_mutex); > > That's not a mutex. > > > + down(&kmmio_init_mutex); > > It's a semaphore. Please do convert it to a mutex. > > Andy, I'd say that addition of new s

Re: [xfs-masters] Re: filesystem corruption on xfs after 2.6.25-rc1 (bisected, powerpc related?)

On Tue, Feb 26, 2008 at 12:52:56AM +0100, Rafael J. Wysocki wrote: > > I'm not suggesting a partial revert; I just wonder which part of the > > change is causing the problem, as part of the debugging process. > > Understood. > > My point is, if that's not practical (whatever the reason), I'd cons

Re: [RFC] mmiotrace full patch, preview 1

On Mon, Feb 25, 2008 at 09:42:00PM -0500, Pavel Roskin wrote: > It looks like a mutex, it acts like a mutex, but it isn't a mutex, it's a > trap for the unwary. Weird. I was annoyed by it before; now I see a > fellow developer actually getting into that trap. > > I'd say, rename DECLARE_MUTEX t

Re: [Lse-tech] Re: a quest for a better scheduler

On Wed, Apr 04, 2001 at 09:44:22AM -0600, Khalid Aziz wrote: > Let me stress that HP scheduler is not meant to be a replacement for the > current scheduler. The HP scheduler patch allows the current scheduler > to be replaced by another scheduler by loading a module in special > cases. HP also ha

Re: CML2 1.0.0 release announcement

In article you wrote: > One of the first things I noticed was it seems noticably slower > than CML1. A make menuconfig in CML1 takes me into the menu > in under a second. (On an already compiled tree). > CML2 takes around 15 seconds before I get th

Re: CML2 1.0.0 release announcement

On Wed, Apr 11, 2001 at 10:16:36PM +0200, Dave Jones wrote: > On Wed, 11 Apr 2001, Christoph Hellwig wrote: > > > > CML2 takes around 15 seconds before I get that far. > > > This is on an Athlon 800 w/512MB. I dread to think how this > > > responds on a 486.

Re: block device snapshot capability

In article <[EMAIL PROTECTED]> you wrote: > Hello all, > > Is anyone aware of ongoing development to provide the capability > to take a snapshot of a block device? It's part of Linux-LVM since version 0.8 and thus part of Linux 2.4. Christoph -- Of course it doesn't work. We've perfo

Re: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2.4.4 -pre2)

In article <[EMAIL PROTECTED]> you wrote: > > When compiling 2.4.3-ac5 (and also 2.4.4-pre2) I get this: > > /usr/src/linux-2.4.3-ac5/include/asm/rwsem.h:26: badly punctuated parameter list > in `#define' > > This appears to be due to some code in rwsem.h that is written for a different > version

Re: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2 .4.4 -pre2)

On Thu, Apr 12, 2001 at 03:08:28PM -0500, [EMAIL PROTECTED] wrote: > >old compiler. The right ifdef seems to be: > > > > > #if __GNUC__ == 2 && __GNUC_MINOR__ < 95 > > > >Could you test it this way? > > Yes, that works for me. Is this the sort of thing you had in mind? Yes. Linus any chance

Re: badly punctuated parameter list in `#define' (2.4.3-ac5 and 2.4.4 -pre2)

On Fri, Apr 13, 2001 at 12:39:39PM +0200, Jamie Lokier wrote: > Christoph Hellwig wrote: > > So the /* old gcc */ part should probably be enabled based on a define for the > > old compiler. The right ifdef seems to be: > > > > #if __GNUC__ == 2 && __GNU

Re: kernel space getcwd()? (using current() to find out cwd)

In article <[EMAIL PROTECTED]> you wrote: > So, a little ignorance being a dangerous thing, I thought I'd be clever > and manually reconstruct the full path by walking up > current->fs->pwd->d_parent and padding d_name to the filename until it > hits root. > > Unfortunatly, this approach causes ke

Re: generic rwsem [Re: Alpha "process table hang"]

In article <[EMAIL PROTECTED]> you wrote: > My generic rwsem should be also cleaner and faster than the generic ones in > 2.4.4pre3 and they can be turned off completly so an architecture can really > takeover with its own asm implementation (while with the 2.4.4pre3 design this > is obviously not

Re: generic rwsem [Re: Alpha "process table hang"]

Hi Andrea, In article <[EMAIL PROTECTED]> you wrote: > I didn't exported rwsem.c if CONFIG_RWSEM_GENERIC is set to n as suggested > by Christoph yet because the old code couldn't be buggy and it's not obvious to > me that the other way around is correct (Christoph are you sure we can export an >

Re: [kbuild-devel] Supplying missing entries for Configure.help, part 2

On Tue, Apr 17, 2001 at 08:54:49PM -0400, Eric S. Raymond wrote: > +Kernel support for JAVA binaries > +CONFIG_BINFMT_JAVA > + If you answer Y here, the kernel's program loader will know how to > + directly execute Java J-code. This option is semi-obsolescent; you > + should probably use CONF

Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list

On Thu, Apr 19, 2001 at 01:45:20PM -0600, Andreas Dilger wrote: > I don't think that the subscription is necessarily the only issue. I'm > subscribed to all of the LVM mailing lists, and still a lot of what I > submit (legitimate bug fixes, and not just features/code cleanup) does > not get added

Re: Your message to linux-lvm awaits moderator approval

On Thu, Apr 19, 2001 at 09:56:52PM +0200, [EMAIL PROTECTED] wrote: > Your mail to 'linux-lvm' with the subject > > Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > >

Re: rwsem.o listed twice as export-objs

In article <[EMAIL PROTECTED]> you wrote: > Hi David, > > please remove rwsem.o from the list of exported objects, if it is > not used. No! The whole point of 'export-objs' is to _always_ list the objects there to make the makefiles smaller and cleaner. Christoph -- Of course it doesn

Re: hundreds of mount --bind mountpoints?

In article <[EMAIL PROTECTED]> you wrote: > Last time we suggested this, people ended up with some OS trying > it and getting worse performance. Which OS? Neither BSD nor SVR4/SVR5 (or even SVR3) do that. > Why? You need to allocate the VFS-inode (vnode in other OSs) and > the on-disk-inode any

Re: SMP: bind process to cpu

In article <[EMAIL PROTECTED]> you wrote: > Hi, > > I run an 3*XEON 550MHz Primergy with 2GB of RAM. > On this machine, i have compiled kernel 2.4.0SMP. > > Is it possible to bind a process to a specific > cpu on this SMP machine (process affinity) ? Linux 2.4 is mostlu ready for process affinity

Re: SMP: bind process to cpu

[Nick, I've added you to the Cc list so you can look at it for future versions of your patch] On Sat, Feb 17, 2001 at 03:13:45PM +0100, Manfred Spraul wrote: > You must also update wake_process_synchroneous(), otherwise you can get > lost wakeups with pipes. > > Something like

Re: Linux 2.4.1-ac15

In article <[EMAIL PROTECTED]> you wrote: > No need for a callin routine, you can get this for free as part of > normal scheduling. The sequence goes :- > > if (use_count == 0) { > module_unregister(); > wait_for_at_least_one_schedule_on_every_cpu(); > if (use_count != 0) { > module_reg

Re: [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com

In article <[EMAIL PROTECTED]> you wrote: > On Wed, Feb 21, 2001 at 02:49:17PM +1100, Richard Gooch wrote: >> You definately can mknod(2) on devfs. [..] > So then why don't we simply create the VG ourself with the right minor number > and use it as we do without devfs? We'll still have a global 2

Re: [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com

On Wed, Feb 21, 2001 at 10:12:25PM -0600, Peter Samuelson wrote: > > [Christoph Hellwig] > > It would be really good to have something devfs-like just for LVM in > > setups that don't use LVM, so we could avoid mounting root read/write > ^^^devf

Re: [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com

On Thu, Feb 22, 2001 at 04:52:51AM -0600, Peter Samuelson wrote: > > [Peter Samuelson] > > > How often do you run MAKEDEV or vgscan? > > [Christoph Hellwig] > > On every bootup, _before_ doing mount -a > > A mere 'vgchange -ay' works fine for *m

Re: [PATCH][CFT] per-process namespaces for Linux

On Mon, Feb 26, 2001 at 08:26:23AM -0800, Peter J. Braam wrote: > - when you login, you get imounted into an environment where you have full > priviliges (except mknod). The "/" of your environment is not a directory > in the Unix tree. > - in this environment the system file systems are availa

Re: [PATCH] reiserfs patch for linux-2.4.2

On Thu, Mar 01, 2001 at 11:01:59AM +1100, Keith Owens wrote: > On Wed, 28 Feb 2001 20:27:33 +0100, > Christoph Hellwig <[EMAIL PROTECTED]> wrote: > >Urgg. limits.h is a userlevel header... > > > >The attached patch will make similar atempts fail (but not this one

Re: [PATCH] reiserfs patch for linux-2.4.2

On Wed, Feb 28, 2001 at 10:16:02PM -0500, Albert D. Cahalan wrote: > Christoph Hellwig writes: > > > Urgg. limits.h is a userlevel header... > > > > The attached patch will make similar atempts fail (but not this one as > > there is also a limits.h in gcc's in

Re: [PATCH] reiserfs patch for linux-2.4.2

On Wed, Feb 28, 2001 at 10:21:30PM +0300, Alexander Zarochentcev wrote: > 6. Using integer constants from limits.h instead of self made ones Urgg. limits.h is a userlevel header... The attached patch will make similar atempts fail (but not this one as there is also a limits.h in gcc's include di

Re: 2.4 and 2GB swap partition limit

Hi Matt, In article <[EMAIL PROTECTED]> you wrote: > My concern is that if there continues to be a 2GB swap partition/file size > limitation, and you can have (as currently #defined) 8 swap partitions, > you're limited to 16GB swap, which then follows a max of 8GB RAM. We'd like > to sell server

Re: Change of policy for future 2.2 driver submissions

In article <[EMAIL PROTECTED]> you wrote: >> In other words, there's no longer any such thing as a "stable" branch. The >> whole point of having separate production and development branches was to have >> one in which each succeeding patch could be counted upon to be more reliable > By your pers

Re: MM/VM todo list

On Fri, Jan 05, 2001 at 02:56:40PM -0200, Marcelo Tosatti wrote: > > * VM: experiment with different active lists / aging pages > > of different ages at different rates + other page replacement > > improvements > > * VM: Quality of Service / fairness / ... improvements > * VM: Use kiobuf IO

Re: MM/VM todo list

On Fri, Jan 05, 2001 at 07:20:24PM -0200, Rik van Riel wrote: > > > * VM: Use kiobuf IO in VM instead buffer_head IO. > > > > I'd vote for killing both bufer_head and kiobuf from VM. > > Lokk at my pageio patch - VM doesn't know about the use of kiobufs > > in the filesystem IO... > > Could b

Re: MM/VM todo list

On Fri, Jan 05, 2001 at 07:27:38PM -0200, Rik van Riel wrote: > > No other then filesystem IO (page/buffercache) is actively tied > > to the VM, so there should be no problems. > > Not right now, no. But if you know what is possible > (and planned) with the kiobuf layer, you should think > twice

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

In article <[EMAIL PROTECTED]> you wrote: > I've put a patch up for testing on the kernel.org mirrors: > > /pub/linux/kernel/people/davem/zerocopy-2.4.0-1.diff.gz > > It provides a framework for zerocopy transmits and delayed > receive fragment coalescing. TUX-1.01 uses this framework. Hi Dave,

Re: Patch (repost): cramfs memory corruption fix

In article <[EMAIL PROTECTED]> you wrote: > Hi Linus, > > On Sun, 7 Jan 2001, Linus Torvalds wrote: >> I wonder what to do about this - the limits are obviously useful, as >> would the "use swap-space as a backing store" thing be. At the same >> time I'd really hate to lose the lean-mean-clean ram

Re: 2.4.0 - sndstat not present

In article <[EMAIL PROTECTED]> you wrote: > i installed 2.4.0 last week and all worked well on my amd-K6-350 > i use a cheap sound card since 2.0.36 and it always worked well too. > it work well now in 2.4.0, BUT , /dev/sndstat report me directory> > and /proc/sound (as noted in documentation) do

Re: 2.4.0 - sndstat not present

On Mon, Jan 08, 2001 at 10:30:39AM -0500, Martin Laberge wrote: > the reference to sndstat and /proc/sound was found in > > drivers/sound/soundcard.c IIRC it is only in the changelogs - and I don't want to play Big Brother on source files ... > thanks for your lights on this topic... > > is th

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Tue, Jan 09, 2001 at 11:23:41AM +0100, Ingo Molnar wrote: > > On Mon, 8 Jan 2001, Rik van Riel wrote: > > > I really think the zerocopy network stuff should be ported to kiobuf > > proper. > > yep, we talked to Stephen Tweedie about this already, but it involves some > changes in kiovec supp

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Tue, Jan 09, 2001 at 02:31:13AM -0800, David S. Miller wrote: >Date: Tue, 9 Jan 2001 11:31:45 +0100 >From: Christoph Hellwig <[EMAIL PROTECTED]> > >Yuck. A new file_opo just to get a few benchmarks right ... I >hope the writepages stuff will not be merg

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

In article <[EMAIL PROTECTED]> you wrote: > On Tue, 9 Jan 2001, Ingo Molnar wrote: >> >> So i do believe that the networking >> code is properly designed in this respect, and this concept goes to the >> highest level of the networking code. > Absolutely. This is w

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Tue, Jan 09, 2001 at 12:55:51PM -0800, Linus Torvalds wrote: > > > On Tue, 9 Jan 2001, Christoph Hellwig wrote: > > > > Also the tuple argument you gave earlier isn't right in this specific case: > > > > when doing sendfile from pagecache to an fs, yo

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Tue, Jan 09, 2001 at 10:38:30AM -0500, Benjamin C.R. LaHaise wrote: > What you're completely ignoring is that sendpages is lacking a huge amount > of functionality that is *needed*. I can't implement clean async io on > top of sendpages -- it'll require keeping 1 task around per outstanding >

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Tue, Jan 09, 2001 at 01:26:44PM -0800, Linus Torvalds wrote: > > > On Tue, 9 Jan 2001, Christoph Hellwig wrote: > > > > > > Look at sendfile(). You do NOT have a "bunch" of pages. > > > > > > Sendfile() is very much a page-at-a-time t

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Wed, Jan 10, 2001 at 12:05:01AM -0800, Linus Torvalds wrote: > > > On Wed, 10 Jan 2001, Christoph Hellwig wrote: > > > > Simple. Because I stated before that I DON'T even want the networking > > to use kiobufs in lower layers. My whole argument is to p

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Tue, Jan 09, 2001 at 12:05:59PM +0100, Ingo Molnar wrote: > > On Tue, 9 Jan 2001, Christoph Hellwig wrote: > > > > 2.4. In any case, the zerocopy code is 'kiovec in spirit' (uses > > > vectors of struct page *, offset, size entities), > > &g

Re: [linux-lvm] Re: *** ANNOUNCEMENT *** LVM 0.9.1 beta1 available at www.sistina.com

On Fri, Jan 12, 2001 at 06:43:23PM -0700, Andreas Dilger wrote: > Anton, you write: > > Have a look at 2.4, arch/sparc64/kernel/ioctl32.c > > Yuk. > > > Would it be possible to clean up the ioctl interface so we dont need > > such large hacks for LVM support? I can do the work but I want to be >

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Thu, Jan 18, 2001 at 01:05:43AM +1100, Rik van Riel wrote: > On Wed, 10 Jan 2001, Christoph Hellwig wrote: > > > Simple. Because I stated before that I DON'T even want the > > networking to use kiobufs in lower layers. My whole argument is > > to pass a kiovec

Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Wed, Jan 17, 2001 at 05:13:31PM -0800, Linus Torvalds wrote: > > > On Thu, 18 Jan 2001, Christoph Hellwig wrote: > > > > /* > > * a simple page,offset,legth tuple like Linus wants it > > */ > > struct kiobuf2 { > >

Re: [Kiobuf-io-devel] Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1

On Fri, Jan 19, 2001 at 08:05:41AM +0530, [EMAIL PROTECTED] wrote: > Shouldn't we have an error / status field too ? Might make sense. Christoph -- Of course it doesn't work. We've performed a software upgrade. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" i

Re: [RFC] generic IO write clustering

In article <[EMAIL PROTECTED]> you wrote: > The write clustering issue has already been discussed (mainly at Miami) > and the agreement, AFAIK, was to implement the write clustering at the > per-address-space writepage() operation. > IMO there are some problems if we implement the write clusterin

Re: [RFC] generic IO write clustering

On Sat, Jan 20, 2001 at 01:24:40PM -0200, Marcelo Tosatti wrote: > In case the metadata was not already cached before ->cluster() (in this > case there is no disk IO at all), ->cluster() will cache it avoiding > further disk accesses by writepage (or writepages()). True. But you have to go throu

Re: [RFC] generic IO write clustering

On Sat, Jan 20, 2001 at 02:00:24PM -0200, Marcelo Tosatti wrote: > > True. But you have to go through ext2_get_branch (under the big kernel > > lock) - if we can do only one logical->physical block translations, > > why doing it multiple times? > > You dont. If the metadata is cached and uptodat

Re: Advanced Linux Kernel/Enterprise Linux Kernel

In article <[EMAIL PROTECTED]> you wrote: > 2) Continuous operation analogous to power & telephone services. > No way. Multics could have a whole bank of memory fail and keep running. > You could add CPUs, memory and IO devices while it was running without > interrupting users' work. Of course,

Re: opl3.o initialization problems in 2.4

In article <[EMAIL PROTECTED]> you wrote: > I continue to see apparent interaction problems between sb.o and opl3.o > during system initialization. Several people have reported problems > with the opl3.o module not loading or not working properly. A > workaround was developed which results in a

Re: KPATCH] Reserve VM for root (was: Re: Looking for better VM)

On Thu, Nov 16, 2000 at 01:51:01PM -0200, Rik van Riel wrote: > > If you think fork() kills the box then ulimit the maximum number > > of user processes (ulimit -u). This is a different issue and a > > bad design in the scheduler (see e.g. Tru64 for a better one). > > My fair scheduler catches th

Re: [PATCH] ALS-110 opl3 and mpu401 under 2.4.0-test10

> 2) The other relates to the uart401 detection. If you build the sb driver > into the kernel and then pass the commandline uart401=1 this is interpreted > as the io parameter for the uart401 module not a command for the sb driver. Of course. Module parameters are _not_ relevant for builtin driv

Re: sound and scsi pci MODULE_DEVICE_TABLE entries? (primary for Alan Cox)

nux 2.4 PCI interface, some cleanups + * Christoph Hellwig <[EMAIL PROTECTED]> + * */ #include @@ -72,18 +80,11 @@ #define GOF_PER_SEC200 -/* - * Define this to enable recording, - * this is curently broken and using it will cause data corruption - * i

Re: sunhme.c patch for new PCI interface (UNTESTED)

In article <[EMAIL PROTECTED]> you wrote: > I never ported it to the new PCI interfaces strictly because when > combined with SBUS it makes the driver initialization look really > sloppy. BTW, what do you think of a new PCI style probing for SBUS? When I hacked on a small sbus driver, I thought

Re: Patch(?): pci_device_id tables for drivers/scsi in 2.4.0-test11

In article <[EMAIL PROTECTED]> you wrote: > --opJtzjQTFsWo+cga > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Here is my first pass at adding pci_device_id tables to all > PCI scsi drivers in linux-2.4.0-test11. It implements a compromise > regarding named i

Re: [KBUILD] Re: PATCH - kbuild documentation.

On Thu, Nov 30, 2000 at 12:36:28AM +, Russell King wrote: > and CONFIG_FOO=y and CONFIG_BAR=m? What about CONFIG_FOO=y and > CONFIG_BAR=y? Do we still support this method? If not, what is the > recommended way of doing this sort of stuff? To do this you need to extend the scheme a little b

Re: [RFC] Configuring synchronous interfaces in Linux

In article <[EMAIL PROTECTED]> you wrote: > Actually; Ethernet badly needs something like this too. I would kill > to be able to do something like: > ifconfig eth0 speed 100 duplex full > o across different networks cards -- I've been thinking about it of > late as I had to battle with thi

Re: [KBUILD] Re: [BUG] 2.4.0-test11-ac3 breaks raid autodetect (was Re: [BUG] raid5 link error? (was [PATCH] raid5 fix after xor.c cleanup))

On Mon, Nov 27, 2000 at 01:18:52PM +1100, Neil Brown wrote: > Thanks for this > > I have looked more deeply, and discovered the error of my ways. > As the Makefiles now stand, all export-objs (OX_OBJS) get linked > before non-export-objs (O_OBJS) in the same directory, independantly > of any

Re: NWFS [PATCH] File organization 2.2.18 and 2.4.0-7

"Jeff V. Merkey" <[EMAIL PROTECTED]> wrote: > I at present have the NWFS utilities and File System drivers as single > source base. Obviously, the way your tree is organized, the file system > driver proper should be in the kernel tree and the file system utitilies > somewhere else. Yes. > Whe

[PATCH] devfs support for LVM

Hi Linus, I've updated my devfs for lvm patch to 2.4.0-test8pre. Here it is. Christoph -- Always remember that you are unique. Just like everyone else. --- linux.orig/drivers/block/lvm.c Fri Jul 14 14:38:29 2000 +++ linux/drivers/block/lvm.c Sun Sep 3 13:54:00 2000 @@ -299,6

Re: [PATCH] devfs support for LVM

On Tue, Sep 05, 2000 at 04:41:26PM -0600, Richard Gooch wrote: > Christoph Hellwig writes: > > Hi Linus, > > I've updated my devfs for lvm patch to 2.4.0-test8pre. > > Here it is. > [...] > > + lvm_devfs_handle = devfs_register( > > + 0 , &q

Re: [PATCH] devfs support for LVM

On Tue, Sep 05, 2000 at 11:51:14PM -0600, Richard Gooch wrote: > > I can't use /dev/lvm, too because this is the name of the control file > > without lvm (and the lvm tools will barf if this is a dircetory. > > Well, how about another directory name? Can you think of something > else that would b

Re: [PATCH] devfs support for LVM

On Wed, Sep 06, 2000 at 03:48:53PM +, Heinz J. Mauelshagen wrote: > > I can add a patch that does full-blown devfs > > checking to the tools, but this needs a lot of work. > > Actually changing the tools to recognize devfs seems fairly simple. > I am already working on it. > > _But_ the LVM M

Re: 2.4.0-test8-pre1 is quite bad / how about integrating Rik's VM

Michael Elizabeth Chastain <[EMAIL PROTECTED]> wrote: > We could use some more infrastructure here. > (1) A 'make randomconfig' tool that generates a random configuration. mconfig -m random, it's even written by you ;) my current mconfig working version is on ftp.openlinux.org/pub/people/hch/mc

Re: [PATCH] for PAS16 functionality for 2.4

In article <[EMAIL PROTECTED]> you wrote: > The PAS16 sound support includes code for the Soundblaster capability on > the card. Yes. > I found an apparent Makefile error which does not enable the > Soundblaster support as anticipated. Adding SB support induces an error > for uart401 being inc

Re: [PATCH] for PAS16 functionality for 2.4

On Sun, Sep 10, 2000 at 09:48:55AM -0500, Thomas Molina wrote: > On Sun, 10 Sep 2000, Christoph Hellwig wrote: > > I know I misunderstand things occasionally, but it looks ok to > me. Isn't that just an artifact of the diff/patch thing? I simply > added sb.o to the l

Re: [PATCH] for PAS16 functionality for 2.4

On Sun, Sep 10, 2000 at 01:54:38PM -0500, Thomas Molina wrote: > I suppose the more basic question is: Should the Soundblaster-specific > code in pas2_card.c be ripped out and leave only PAS-specific code in > the PAS driver? IMHO you should add some _more_ code to pas2_card.c so the sb stuff is

<    1   2   3   4   5   6   7   8   9   10   >