Re: artificial latency for a network interface
> > I wanted to do that using two tun devices. > > I had hoped to have a routing like this: > > > > <-> eth0 <-> tun0 <-> userspace, waiting queue <-> tun1 <-> eth1 > >yes, that works very well. A userspace app sits on top of the >tun/tap device and pulls out packets, delays them and reinjects >them. Right. And you don't even need tun1. Just write them back to tun0. >The problem is routing: when you send the packet back to the >kernel, it sends it straight back to you. You need to rewrite >the headers, which is a pain. True. Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] http://bluez.sf.net http://vtun.sf.net - 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/lkml/
Re: artificial latency for a network interface
I wanted to do that using two tun devices. I had hoped to have a routing like this: - eth0 - tun0 - userspace, waiting queue - tun1 - eth1 yes, that works very well. A userspace app sits on top of the tun/tap device and pulls out packets, delays them and reinjects them. Right. And you don't even need tun1. Just write them back to tun0. The problem is routing: when you send the packet back to the kernel, it sends it straight back to you. You need to rewrite the headers, which is a pain. True. Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] http://bluez.sf.net http://vtun.sf.net - 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/lkml/
Re: What is the best way for multiple net_devices
>Any examples of drivers and apps that do this cleanly. The ones I have seen are not. TUN/TAP driver and tuncfg utility http://vtun.sf.net/tun Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] http://bluez.sf.net http://vtun.sf.net - 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/lkml/
Re: What is the best way for multiple net_devices
Any examples of drivers and apps that do this cleanly. The ones I have seen are not. TUN/TAP driver and tuncfg utility http://vtun.sf.net/tun Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] http://bluez.sf.net http://vtun.sf.net - 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/lkml/
Re: Configure.help entries for Bluetooth (updated)
>Okay, I'll bite. Ouch that hurts ;) >What's HCI stand for? >I'm guessing it ends in "Connection Interface", but the H has me stumped. Wrong guess. HCI - Host Controller Interface. People who use Bluetooth would know. HCI is the basic thing in Bluetooth world. I don't think explaining that abbreviation would help in kernel configuration. Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - 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/lkml/
RE: Undocumented configuration symbols in 2.4.6pre2
Randy, >Could you make these 5 instances of "Not unsure" be more palatable and less confusing >? Oops, blind cut without reading carefully :). Thanks Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - 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/lkml/
Configure.help entries for Bluetooth (updated)
CONFIG_BLUEZ Bluetooth is low-cost, low-power, short-range wireless technology. It was designed as a replacement for cables and other short-range technologies like IrDA. Bluetooth operates in personal area range that typically extends up to 10 meters. More information about Bluetooth can be found at http://www.bluetooth.com Linux Bluetooth subsystem consist of several layers: HCI Core (device and connection manager, scheduler) HCI Device drivers (interface to the hardware) L2CAP Module (L2CAP protocol) Say Y here to enable Linux Bluetooth support and to build HCI Core layer. To use Linux Bluetooth subsystem, you will need several user-space utilities like hciconfig and hcid. These utilities and updates to Bluetooth kernel modules are provided in the BlueZ package. For more information, see http://bluez.sf.net. If you want to compile HCI Core as module (hci.o) say M here. Not sure ? say N. CONFIG_BLUEZ_L2CAP L2CAP (Logical Link Control and Adaptation Protocol) provides connection oriented and connection-less data transport. L2CAP support is required for most Bluetooth applications. Say Y here to compile L2CAP support into the kernel or say M to compile it as module (l2cap.o). Not sure ? say M. CONFIG_BLUEZ_HCIUART Bluetooth HCI UART driver. This driver is required if you want to use Bluetooth devices with serial port interface. Say Y here to compile support for Bluetooth UART devices into the kernel or say M to compile it as module (hci_uart.o). Not sure ? say M. CONFIG_BLUEZ_HCIUSB Bluetooth HCI USB driver. This driver is required if you want to use Bluetooth devices with USB interface. Say Y here to compile support for Bluetooth USB devices into the kernel or say M to compile it as module (hci_usb.o). Not sure ? say M. CONFIG_BLUEZ_HCIEMU Bluetooth Virtual HCI device driver. This driver is required if you want to use HCI Emulation software. Say Y here to compile support for Virtual HCI devices into the kernel or say M to compile it as module (hci_usb.o). Not sure ? say M. Thanks Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - 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/lkml/
RE: Undocumented configuration symbols in 2.4.6pre2
Randy, Could you make these 5 instances of Not unsure be more palatable and less confusing ? Oops, blind cutpast without reading carefully :). Thanks Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - 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/lkml/
Re: Configure.help entries for Bluetooth (updated)
Okay, I'll bite. Ouch that hurts ;) What's HCI stand for? I'm guessing it ends in Connection Interface, but the H has me stumped. Wrong guess. HCI - Host Controller Interface. People who use Bluetooth would know. HCI is the basic thing in Bluetooth world. I don't think explaining that abbreviation would help in kernel configuration. Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - 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/lkml/
Configure.help entries for Bluetooth (updated)
CONFIG_BLUEZ Bluetooth is low-cost, low-power, short-range wireless technology. It was designed as a replacement for cables and other short-range technologies like IrDA. Bluetooth operates in personal area range that typically extends up to 10 meters. More information about Bluetooth can be found at http://www.bluetooth.com Linux Bluetooth subsystem consist of several layers: HCI Core (device and connection manager, scheduler) HCI Device drivers (interface to the hardware) L2CAP Module (L2CAP protocol) Say Y here to enable Linux Bluetooth support and to build HCI Core layer. To use Linux Bluetooth subsystem, you will need several user-space utilities like hciconfig and hcid. These utilities and updates to Bluetooth kernel modules are provided in the BlueZ package. For more information, see http://bluez.sf.net. If you want to compile HCI Core as module (hci.o) say M here. Not sure ? say N. CONFIG_BLUEZ_L2CAP L2CAP (Logical Link Control and Adaptation Protocol) provides connection oriented and connection-less data transport. L2CAP support is required for most Bluetooth applications. Say Y here to compile L2CAP support into the kernel or say M to compile it as module (l2cap.o). Not sure ? say M. CONFIG_BLUEZ_HCIUART Bluetooth HCI UART driver. This driver is required if you want to use Bluetooth devices with serial port interface. Say Y here to compile support for Bluetooth UART devices into the kernel or say M to compile it as module (hci_uart.o). Not sure ? say M. CONFIG_BLUEZ_HCIUSB Bluetooth HCI USB driver. This driver is required if you want to use Bluetooth devices with USB interface. Say Y here to compile support for Bluetooth USB devices into the kernel or say M to compile it as module (hci_usb.o). Not sure ? say M. CONFIG_BLUEZ_HCIEMU Bluetooth Virtual HCI device driver. This driver is required if you want to use HCI Emulation software. Say Y here to compile support for Virtual HCI devices into the kernel or say M to compile it as module (hci_usb.o). Not sure ? say M. Thanks Max Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - 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/lkml/
test9-pre7 crash
Hi Folks, Sorry if already known. Here is oops I've got on test9-pre7. Not sure what triggered this. As usual when I install new test kernel I do silly simple stress stuff : hdparm -t /dev/sdaX or /dev/hdaX (couple of times) memspeed 150(megs) 10(times) (swaper and mem stress) tcpspeed and udpspeed on loopback (net code stress) And then after a while (1-5 mins) I've started getting crashes, they all looked the same. That's Compaq PIII/124/Adaptec2940/EEpro100(module)/USB (module). 2.4.0-test8 works just fine. So, one of the crashes: Unable to handle kernel NULL pointer dereference at virtual address 0009 c0139902 *pde = Oops: CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: 0009 ebx: ecx: 000d edx: 0001 esi: edi: ebp: 0009 esp: c73ebf08 ds: 0018 es: 0018 ss: 0018 Process login (pid: 655, stackpage=c73eb000) Stack: c73ea000 0001 000d 000f c0139a33 0001 0009 c73ebf48 c73ebf4c c73ea000 0001 0001 c73ea000 c0139ca3 0001 0001 c7dd4660 c73ebfb8 Call Trace: [] [] [] [] Code: 8b 45 00 85 c0 7c 59 e8 9a 25 ff ff 89 c6 bb 20 00 00 00 85 >>EIP; c0139902<= Trace; c0139a33 Trace; c0139ca3 Trace; c0118a6e Trace; c0108d3f Code; c0139902 <_EIP>: Code; c0139902<= 0: 8b 45 00 mov0x0(%ebp),%eax <= Code; c0139905 3: 85 c0 test %eax,%eax Code; c0139907 5: 7c 59 jl 60 <_EIP+0x60> c0139962 Code; c0139909 7: e8 9a 25 ff ffcall 25a6 <_EIP+0x25a6> c012bea8 Code; c013990e c: 89 c6 mov%eax,%esi Code; c0139910 e: bb 20 00 00 00mov$0x20,%ebx Code; c0139915 13: 85 00 test %eax,(%eax) Max P.S. CC replies please I'm not on the list. Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
test9-pre7 crash
Hi Folks, Sorry if already known. Here is oops I've got on test9-pre7. Not sure what triggered this. As usual when I install new test kernel I do silly simple stress stuff : hdparm -t /dev/sdaX or /dev/hdaX (couple of times) memspeed 150(megs) 10(times) (swaper and mem stress) tcpspeed and udpspeed on loopback (net code stress) And then after a while (1-5 mins) I've started getting crashes, they all looked the same. That's Compaq PIII/124/Adaptec2940/EEpro100(module)/USB (module). 2.4.0-test8 works just fine. So, one of the crashes: Unable to handle kernel NULL pointer dereference at virtual address 0009 c0139902 *pde = Oops: CPU:0 EIP:0010:[c0139902] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: 0009 ebx: ecx: 000d edx: 0001 esi: edi: ebp: 0009 esp: c73ebf08 ds: 0018 es: 0018 ss: 0018 Process login (pid: 655, stackpage=c73eb000) Stack: c73ea000 0001 000d 000f c0139a33 0001 0009 c73ebf48 c73ebf4c c73ea000 0001 0001 c73ea000 c0139ca3 0001 0001 c7dd4660 c73ebfb8 Call Trace: [c0139a33] [c0139ca3] [c0118a6e] [c0108d3f] Code: 8b 45 00 85 c0 7c 59 e8 9a 25 ff ff 89 c6 bb 20 00 00 00 85 EIP; c0139902 do_pollfd+2e/b4 = Trace; c0139a33 do_poll+ab/e8 Trace; c0139ca3 sys_poll+233/350 Trace; c0118a6e do_softirq+4e/74 Trace; c0108d3f system_call+33/38 Code; c0139902 do_pollfd+2e/b4 _EIP: Code; c0139902 do_pollfd+2e/b4 = 0: 8b 45 00 mov0x0(%ebp),%eax = Code; c0139905 do_pollfd+31/b4 3: 85 c0 test %eax,%eax Code; c0139907 do_pollfd+33/b4 5: 7c 59 jl 60 _EIP+0x60 c0139962 do_pollfd+8e/b4 Code; c0139909 do_pollfd+35/b4 7: e8 9a 25 ff ffcall 25a6 _EIP+0x25a6 c012bea8 fget+0/28 Code; c013990e do_pollfd+3a/b4 c: 89 c6 mov%eax,%esi Code; c0139910 do_pollfd+3c/b4 e: bb 20 00 00 00mov$0x20,%ebx Code; c0139915 do_pollfd+41/b4 13: 85 00 test %eax,(%eax) Max P.S. CC replies please I'm not on the list. Maksim Krasnyanskiy Senior Kernel Engineer Qualcomm Incorporated [EMAIL PROTECTED] (408) 557-1092 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
