O_NONBLOCK supposedly hits the entire 'ofile' and not just the fd:
http://cr.yp.to/unix/nonblock.html
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
-
To unsubscribe from this list: send the line "unsubs
On Fri, Feb 02, 2007 at 03:37:09PM -0800, Davide Libenzi wrote:
> Since I still think that the many-thousands potential async operations
> coming from network sockets are better handled with a classical event
> machanism [1], and since smooth integration of new async syscall into the
> standard
On Mon, Feb 05, 2007 at 01:57:15PM -0800, Linus Torvalds wrote:
> I doubt very many people want to do that. It would tend to simply be nicer
> to do
>
> async(poll);
Yeah - I saw that technique being mentioned later on in the thread, and it
would work, I think.
To make up for the waste o
On Fri, Feb 09, 2007 at 02:33:01PM -0800, Linus Torvalds wrote:
> - IF the system call blocks, we call the architecture-specific
>"schedule_async()" function before we even get any scheduler locks, and
>it can just do a fork() at that time, and let the *child* return to the
>origin
On Tue, Feb 13, 2007 at 09:58:48AM -0500, Benjamin LaHaise wrote:
> not present is mandatory). I have looked into exactly this approach, and
> it's only cheaper if the code is incomplete. Linux's native threads are
> pretty damned good.
Cheaper in time or in memory? Iow, would you be able to
On Thu, Feb 15, 2007 at 09:42:32AM -0800, Linus Torvalds wrote:
> We know one interface: the current aio_read() one. Nobody really _likes_
[...]
> Others? We don't know yet. And exposing complex interfaces that may not be
> the right ones is much *worse* than exposing simple interfaces (that
>
On Tue, Feb 20, 2007 at 11:50:13AM +0100, Andi Kleen wrote:
> P4s are pretty slow at taking locks (or rather doing atomical operations)
> and there are several of them in this path. You could try it with a UP
> kernel. Actually hotunplugging the other virtual CPU should be sufficient
> with recent
On Tue, Feb 20, 2007 at 07:41:25PM +0300, Evgeniy Polyakov wrote:
> It can be recvfrom only problem - syscall overhead on my p4 (core duo,
> debian testing) is bout 300 usec - to test I ran read('dev/zero', &data,
> 0) in a loop.
nsec I assume?
The usec numbers for read(fd, &c, 0) where fd is /d
On Tue, Feb 20, 2007 at 09:48:59PM +0300, Evgeniy Polyakov wrote:
> Likely first overhead related to cache population or gamma-ray radiation.
> If it happens only one (it does in my test), then everything is ok I
> think. Bert, how frequently you get that long recvfrom()?
I have plotted the avera
On Tue, Feb 20, 2007 at 02:40:40PM -0500, Benjamin LaHaise wrote:
> Make sure your system is idle. Userspace bloat means that *lots* of idle
> activity occurs in between timer ticks on recent distributions -- all those
You hit the nail on the head. I had previously measured with X shut down,
b
On Tue, Feb 20, 2007 at 02:02:00PM -0800, Rick Jones wrote:
> The slope appears to be flattening-out the farther out to the right it
> goes. Perhaps that is the length of time it takes to take all the
> requisite cache misses.
The rate of flattening out appears to correlate with the number of
On Thu, Feb 01, 2007 at 03:11:03PM +0100, Martin Klejch wrote:
>I am a linux user (distro Ubuntu 6.10) with a 2.6.17.10-generic
> kernel running on my Acer TravelMate 4672LMi.
> I found a line "Please report the result to linux-kernel to fix this
> permanently" in my /var/log/kern.log but ha
On Tue, Jan 30, 2007 at 01:39:45PM -0700, Zach Brown wrote:
> sys_asys_submit() is added to let userspace submit asynchronous system calls.
> It specifies the system call number and arguments. A fibril is constructed
> for
> each call. Each starts with a stack which executes the given system ca
On Thu, Feb 01, 2007 at 01:29:41PM -0800, Zach Brown wrote:
> >I want to try it on from a userspace perspective.
>
> Frankly, I'm not sure its ready for that yet. You're welcome to give
> it a try, but it's early enough that you're sure to hit problems
> almost immediately.
I'm counting on
On Fri, Feb 02, 2007 at 03:17:57PM -0800, Linus Torvalds wrote:
> threads. But you need to look at what it is we parallelize here, and ask
> yourself why we're doing what we're doing, and why people aren't *already*
> just using a separate thread for it.
Partially this is for the bad reason tha
On Sun, Dec 03, 2006 at 05:53:23PM -0800, Bill Huey wrote:
> [8264, 996648, 0] {inode_init_once, fs/inode.c, 196}
> [8552, 996648, 0] {inode_init_once, fs/inode.c, 193}
Impressive, Bill!
How tightly is your work bound to -rt? Iow, any chance of separating the
two? Or shou
On Mon, Dec 04, 2006 at 07:30:33AM -0500, Josef 'Jeff' Sipek wrote:
> The following patches are in a git repo at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jsipek/unionfs.git
Jeff,
Do you have a pointer to a quick blurb on this work?
Thanks.
--
http://www.PowerDNS.com Open source
On Thu, Jan 11, 2007 at 07:50:26AM -0800, Linus Torvalds wrote:
> Yes. O_DIRECT is really fundamentally broken. There's just no way to fix
> it sanely. Except by teaching people not to use it, and making the normal
Does this mean that it will eat data today? Or that it is broken because it
requi
On Thu, Jan 11, 2007 at 01:25:16AM -0700, Sean Reifschneider wrote:
> Nope, I haven't looked in strace at all. It's definitely making it to
> user-space. The code in question is (abbreviated):
>
>if (select(0, (fd_set *)0, (fd_set *)0, (fd_set *)0, &t) != 0) {
> PyErr_SetFromErrno(PyE
On Mon, Nov 27, 2006 at 06:26:34PM +, Eric Van Hensbergen wrote:
> This is the first cut of a device-mapper target which provides a write-back
> or write-through block cache. It is intended to be used in conjunction with
> remote block devices such as iSCSI or ATA-over-Ethernet, particularly i
On Sat, Jun 16, 2007 at 08:10:53PM -0700, Linus Torvalds wrote:
> This is where we started. The same way you seem to think that "freedom"
> has only the meaning *you* and the FSF give it, and that somehow the
> spirit of the GPL includes the "four freedoms" that aren't even
> _mentioned_ in it.
Greg, Kay, kernel people,
Today I booted 2.6.22-rc2 on Ubunty Edgy Eft, and lsusb died on me:
[EMAIL PROTECTED]:~$ lsusb
[EMAIL PROTECTED]:~$ sudo lsusb
[EMAIL PROTECTED]:~$
This behaviour persists in rc4. This might be udev related. I'm running:
ii udev 093-0
On Sun, May 27, 2007 at 04:42:35AM +0200, Kay Sievers wrote:
> > Any clues? Please let me know how I can help solve this problem!
>
> It works fine for me here. Do you have CONFIG_USB_DEVICE_CLASS=y set?
Ah, I have not. However, this setting was not present in 2.6.21-rc3, from
which configuration
> the separate class device. How does that help text sound?
>
> This option provides backward compatibility for systems where
> usbfs is not mounted, and no udev rule like this exists:
> SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \
> NAME="bus/usb/$env{BUSNUM}/$env{
On Sun, May 27, 2007 at 04:34:37PM +0200, Kay Sievers wrote:
> older kernels. That's all, and correctly configured kernels don't break
> anything.
>
> > So instead of papering this breakage over with cleverly worded help texts
> > that suggest a solution, how about we set USB_DEVICE_CLASS to 'y' b
On Sun, May 27, 2007 at 06:10:41PM +0200, Jesper Juhl wrote:
> >bool "USB device class-devices (DEPRECATED)"
> >depends on USB
> >- default n
> >+ default y
>
> It puzzles me why a deprecated option should be default 'Y'...
Because if it defaults to 'n', a 'make oldcon
Con,
Recent kernel versions have real problems for me on the interactivity front,
with even a simple 'make' of my C++ program (PowerDNS) causing Firefox to
slow down to a crawl.
RSDL fixed all that, the system is noticeably snappier.
As a case in point, I used to notice when a compile was done b
On Sat, Mar 03, 2007 at 04:30:56PM -0500, Rik van Riel wrote:
> The user has been accessing the kernel tree over and over
> again, for hours on end (compile testing a patch). Along
> comes a backup program, that tells you to evict the whole
> thing from the cache.
This is arguably due to a linux
On Sat, Mar 03, 2007 at 11:30:49PM +0100, Arnd Bergmann wrote:
> It might be nicer to make this
>
> for (;;)
> asm volatile ("idle");
This looks remarkably like relax_cpu()
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl
On Sat, Mar 03, 2007 at 02:26:09PM -0800, Andrew Morton wrote:
> > > It is *not* a global instruction. It uses setenv, so the user's policy
> > > affects only the target process and its forked children.
> >
> > ... and all other processes accessing the same file(s)!
> >
> > Your library and the
101 - 130 of 130 matches
Mail list logo
