On Wed, Jun 28, 2006 at 08:47:09PM -0700, David Miller wrote:
> You can save yourself that hassle by informing the site admin
> of the affected site that they have a firewall that misinterprets
> the RFC standard window scaling field of the TCP headers. These
> devices assume it is zero because th
This patch improves the statistics returned from bcm43xx_get_wireless_stats.
The signal level comes
from smoothing the rssi value returned by the firmware. The quality value is a
hack derived from the
smoothed rssi value and an assumed rssi_max of -25. If anyone has a better
value, please let m
From: CaT <[EMAIL PROTECTED]>
Date: Thu, 29 Jun 2006 13:09:23 +1000
> Yup. Must've. Just tried it now and setting tcp_window_scaling to 0
> makes the site load. Sorry about that. Looks like I'll have to remember
> to make sure that gets set to zero on any servers I wind up having to
> upgrade to 2
On Wed, 28 Jun 2006 16:07:22 PDT, "Ron Mercer" wrote:
> >
> > Is the device hotpluggable? If so, this:
> >
> > qdev->index = cards_found;
> >
> > in the probe() handler might do odd things - it'll just keep
> > increasing as the card is removed and re-added.
> >
> > iirc, that's a commo
On Wed, Jun 28, 2006 at 07:46:27PM -0700, David Miller wrote:
> From: CaT <[EMAIL PROTECTED]>
> Date: Thu, 29 Jun 2006 11:59:15 +1000
>
> > Now I found a thread about tcp window scaling affecting the loading of
> > some sites but I fail to load the above site with
> > /proc/sys/net/ipv4/tcp_adv_wi
From: CaT <[EMAIL PROTECTED]>
Date: Thu, 29 Jun 2006 11:59:15 +1000
> Now I found a thread about tcp window scaling affecting the loading of
> some sites but I fail to load the above site with
> /proc/sys/net/ipv4/tcp_adv_win_scale set to 6 and 2 under 2.6.17.1
> whilst it works just fine with the
Add support for the Cicada 8201 PHY, a.k.a Vitesse VSC8201. This PHY is
present on the MPC8349mITX.
Signed-off-by: Kim Phillips <[EMAIL PROTECTED]>
Signed-off-by: Andy Fleming <[EMAIL PROTECTED]>
---
drivers/net/phy/cicada.c | 42 --
1 files changed, 3
I had recently upgraded to 2.6.17.1 and tried to go to
http://submit.spam.acma.gov.au/acma_submit.cgi?lang=EN
to report an australian spammer. Unfortunately the loading of the
webpage cuts out at 5472 bytes. I can repeat this each and every time
under 2.6.17.1 with
( echo 'get /acma_submit.cgi?l
Ron Mercer wrote:
Is the device hotpluggable? If so, this:
qdev->index = cards_found;
in the probe() handler might do odd things - it'll just keep
increasing as the card is removed and re-added.
iirc, that's a common problem with net drivers. AFAICT it'll
cause only cosmetic oddi
Daniel Lezcano <[EMAIL PROTECTED]> writes:
> Andrey Savochkin wrote:
>
>> Ok, fine.
>> Now I'm working on socket code.
>> We still have a question about implicit vs explicit function parameters.
>> This question becomes more important for sockets: if we want to allow to use
>> sockets belonging to
James Morris <[EMAIL PROTECTED]> writes:
> On Wed, 28 Jun 2006, Daniel Lezcano wrote:
>
>> The attached patch can have some part interesting for you for the socket
>> tagging. It is in the IPV4 isolation (part 5/6). With this and the private
>> routing table you will probably have a good IPV4 isol
An assert statement near the start of handle_irq_noise in the softmac version of bcm43xx_main.c is
there to protect against out of bound addressing using variable bcm->noisecalc.nr_samples. The
arrays in question have a dimension of 8, thus the value must be < 8.
Signed-Off-By: Larry.Finger <[E
"Miles Lane" <[EMAIL PROTECTED]> wrote:
>
> BUG: unable to handle kernel NULL pointer dereference at virtual
> address 0020
> printing eip:
> f8d21f6e
> *pde =
> Oops: [#1]
> 4K_STACKS PREEMPT
> last sysfs file: /devices/system/cpu/cpu0/cpufreq/scaling_setspeed
> Modules linked i
Jeff Garzik wrote:
> Caitlin Bestler wrote:
>> Jeff Garzik wrote:
>>> Caitlin Bestler wrote:
But hardware iSCSI implementations, which already exist, do not
work through normal sockets.
>
>>> No, they work through normal SCSI stack...
>
>> Correct.
>>
>> But they then interface to the
Caitlin Bestler wrote:
Jeff Garzik wrote:
Caitlin Bestler wrote:
But hardware iSCSI implementations, which already exist, do not work
through normal sockets.
No, they work through normal SCSI stack...
Correct.
But they then interface to the network using none of the network stack.
The no
"Ron Mercer" <[EMAIL PROTECTED]> wrote:
>
> >
> > Is the device hotpluggable? If so, this:
> >
> > qdev->index = cards_found;
> >
> > in the probe() handler might do odd things - it'll just keep
> > increasing as the card is removed and re-added.
> >
> > iirc, that's a common problem wit
>
> Is the device hotpluggable? If so, this:
>
> qdev->index = cards_found;
>
> in the probe() handler might do odd things - it'll just keep
> increasing as the card is removed and re-added.
>
> iirc, that's a common problem with net drivers. AFAICT it'll
> cause only cosmetic odditi
On Wed, 28 Jun 2006, Daniel Lezcano wrote:
> The attached patch can have some part interesting for you for the socket
> tagging. It is in the IPV4 isolation (part 5/6). With this and the private
> routing table you will probably have a good IPV4 isolation.
Please send patches inline, do not attac
Hi Dave,
This patch makes a needlessly global struct static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Signed-off-by: Samuel Ortiz <[EMAIL PROTECTED]>
---
drivers/net/irda/mcs7780.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/irda/mcs7780.c b/driver
Andrey Savochkin wrote:
Ok, fine.
Now I'm working on socket code.
We still have a question about implicit vs explicit function parameters.
This question becomes more important for sockets: if we want to allow to use
sockets belonging to namespaces other than the current one, we need to do
somet
Li Yang-r58472 <[EMAIL PROTECTED]> wrote:
>
> This is a gigabit Ethernet driver for Freescale QE(QUICC ENGINE) SOC. QE can
> be found on PowerQUICC II pro family.
>
>
>
> diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
> index bdaaad8..ebbb218 100644
> --- a/drivers/net/Kconfig
> +++ b/dr
Jeff Garzik wrote:
> Caitlin Bestler wrote:
>> [EMAIL PROTECTED] wrote:
>>> From: Steve Wise <[EMAIL PROTECTED]>
>>> Date: Wed, 28 Jun 2006 09:54:57 -0500
>>>
Doesn't iSCSI have this same issue?
>>> Software iSCSI implementations don't have the issue because they go
>>> through the stack usin
Caitlin Bestler wrote:
[EMAIL PROTECTED] wrote:
From: Steve Wise <[EMAIL PROTECTED]>
Date: Wed, 28 Jun 2006 09:54:57 -0500
Doesn't iSCSI have this same issue?
Software iSCSI implementations don't have the issue because
they go through the stack using normal sockets and normal
device send and
Well, I doubt it is a bcm43xx issue. But maybe. Not sure.
Do you run some QoS stuff? Some other quota stuff?
Yes, a special QoS rule that cuts off connections from devices that do
not use a GPL driver.
Long life to the penguin !
Soon, my HiFi will cut off the whole drum section of the DRM son
On Wednesday 28 June 2006 21:27, Francois Barre wrote:
> Hi all,
>
> Sorry for answering years after the patch post, I didn't have time to
> test this take2 patch before. I had a first look at it a couple of
> days ago, but... you know, that was not my day.
>
> > Well, it does not work 100%, but
Hi all,
Sorry for answering years after the patch post, I didn't have time to
test this take2 patch before. I had a first look at it a couple of
days ago, but... you know, that was not my day.
Well, it does not work 100%, but at least it's very promising.
We are able to create a bssid and corre
On Wed, 2006-06-28 at 11:36 -0700, David Miller wrote:
> From: Steve Wise <[EMAIL PROTECTED]>
> Date: Wed, 28 Jun 2006 09:54:57 -0500
>
> > Doesn't iSCSI have this same issue?
>
> Software iSCSI implementations don't have the issue because
> they go through the stack using normal sockets and norm
Lower mac_suspend timeout.
This timeout won't ever trigger, if the hardware and driver is
not horribly faulty. It's just a safety net to not lock up the
kernel on bugs.
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
Index: wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
===
[EMAIL PROTECTED] wrote:
> From: Steve Wise <[EMAIL PROTECTED]>
> Date: Wed, 28 Jun 2006 09:54:57 -0500
>
>> Doesn't iSCSI have this same issue?
>
> Software iSCSI implementations don't have the issue because
> they go through the stack using normal sockets and normal
> device send and receive.
On Wed, Jun 28, 2006 at 12:14:41PM -0600, Eric W. Biederman wrote:
> Andrey Savochkin <[EMAIL PROTECTED]> writes:
>
> > On Wed, Jun 28, 2006 at 10:51:26AM -0600, Eric W. Biederman wrote:
> >> Andrey Savochkin <[EMAIL PROTECTED]> writes:
> >>
> >> > One possible option to resolve this question is
This fixes mac_suspend reference counting for
ifconfig up
ifconfig down
ifconfig up
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
Index: wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c
===
--- wireless-dev.orig/dr
From: Steve Wise <[EMAIL PROTECTED]>
Date: Wed, 28 Jun 2006 09:54:57 -0500
> Doesn't iSCSI have this same issue?
Software iSCSI implementations don't have the issue because
they go through the stack using normal sockets and normal
device send and receive.
-
To unsubscribe from this list: send the
This fixes mac_suspend reference counting for
ifconfig up
ifconfig down
ifconfig up
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_main.c
===
--- wireless-2.6.orig/drivers/n
Comments below:
On 6/29/06, Adrian Bunk <[EMAIL PROTECTED]> wrote:
This patch contains the following possible cleanups:
- sysctl.c: the Kconfig rules already disallow CONFIG_SYSCTL=n,
there's no need for an additional check
Agree
- proper extern declarations for some variables in
Andrey Savochkin <[EMAIL PROTECTED]> writes:
>> In a slightly different vein your second patch introduced a lot
>> of #ifdef CONFIG_NET_NS in C files. That is something we need to look
>> closely
>> at.
>>
>> So I think the abstraction that we use to access per network namespace
>> variables ne
Andrey Savochkin <[EMAIL PROTECTED]> writes:
> Hi Eric,
>
> On Wed, Jun 28, 2006 at 10:51:26AM -0600, Eric W. Biederman wrote:
>> Andrey Savochkin <[EMAIL PROTECTED]> writes:
>>
>> > One possible option to resolve this question is to show 2 relatively short
>> > patches just introducing namespace
This patch adds voluntary preemption points into the
PHY calibration loops to allow non-CONFIG_PREEMPT machines
to not suffer from huge delays.
CONFIG_PREEMPT machines are already fine, because all this
code is run in non-atomic process context.
Signed-off-by: Michael Buesch <[EMAIL PROTECTED]>
I
On Wednesday 28 June 2006 19:32, Larry Finger wrote:
> Michael Buesch wrote:
> > On Wednesday 28 June 2006 18:04, Larry Finger wrote:
> >
> > Oh, well. Forget it all.
> > I remembered the code wrong.
> > At the moment I looked at the code and it has the opposite semantics.
> > It loops to wait for
Minor change in shutdown logic to effect a link down.
Update version to 1.4.43.
Signed-off-by: Michael Chan <[EMAIL PROTECTED]>
diff --git a/drivers/net/bnx2.c b/drivers/net/bnx2.c
index e59cb59..d55b0f7 100644
--- a/drivers/net/bnx2.c
+++ b/drivers/net/bnx2.c
@@ -57,8 +57,8 @@
#define DRV_M
Change all dev_kfree_skb_irq() and dev_kfree_skb_any() to
dev_kfree_skb(). These calls are never used in irq context.
Signed-off-by: Michael Chan <[EMAIL PROTECTED]>
diff --git a/drivers/net/bnx2.c b/drivers/net/bnx2.c
index e89d5df..e59cb59 100644
--- a/drivers/net/bnx2.c
+++ b/drivers/net/bnx
Andrey Savochkin <[EMAIL PROTECTED]> writes:
>> A general pattern that happens in cleanups is the discovery
>> that code using an old interface in a problematic way really
>> could be done much better another way. I didn't dig enough
>> to see if that was the case in any of the code that you chan
On Wed, Jun 28, 2006 at 09:22:40PM +0400, Andrey Savochkin wrote:
> Hi Eric,
>
> On Wed, Jun 28, 2006 at 10:51:26AM -0600, Eric W. Biederman wrote:
> > Andrey Savochkin <[EMAIL PROTECTED]> writes:
> >
> > > One possible option to resolve this question is to show 2
> > > relatively short patches j
For easier review, a tarball of drivers/net/wireless/zd1211rw is available here:
http://www.kernel.org/pub/linux/kernel/people/linville/zd1211rw.tar.gz
>From Daniel's initial zd1211rw changelog:
[PATCH] ZyDAS ZD1211 USB-WLAN driver
There are 60+ USB wifi adapters available on th
Michael Buesch wrote:
On Wednesday 28 June 2006 18:04, Larry Finger wrote:
Oh, well. Forget it all.
I remembered the code wrong.
At the moment I looked at the code and it has the opposite semantics.
It loops to wait for the READY bit to appear.
Well, I would say your old device simply takes thi
Hi Eric,
On Wed, Jun 28, 2006 at 10:51:26AM -0600, Eric W. Biederman wrote:
> Andrey Savochkin <[EMAIL PROTECTED]> writes:
>
> > One possible option to resolve this question is to show 2 relatively short
> > patches just introducing namespaces for sockets in 2 ways: with explicit
> > function par
Daniel Lezcano wrote:
Kirill Korotaev wrote:
Structures related to IPv4 rounting (FIB and routing cache)
are made per-namespace.
Hi Andrey,
if the ressources are private to the namespace, how do you will
handle NFS mounted before creating the network namespace ? Do you
take care of that
Kirill Korotaev wrote:
Structures related to IPv4 rounting (FIB and routing cache)
are made per-namespace.
Hi Andrey,
if the ressources are private to the namespace, how do you will
handle NFS mounted before creating the network namespace ? Do you
take care of that or simply assume you can'
On Wed, Jun 28, 2006 at 06:19:00PM +0400, Andrey Savochkin wrote:
> Hi Jamal,
>
> On Wed, Jun 28, 2006 at 09:53:23AM -0400, jamal wrote:
> >
> > On Wed, 2006-28-06 at 15:36 +0200, Herbert Poetzl wrote:
> >
> > > note: personally I'm absolutely not against virtualizing
> > > the device names so t
On Wed, Jun 28, 2006 at 10:40:10AM -0400, Lennart Sorensen wrote:
> On Fri, Jun 23, 2006 at 02:32:12PM -0700, Don Fry wrote:
> > This set of changes combines the work done by Len Sorensen and myself to
> > add compile time support for NAPI for the pcnet32 driver. I have tested
> > it on ia32 and p
On Wed, Jun 28, 2006 at 09:36:40AM -0600, Eric W. Biederman wrote:
> Herbert Poetzl <[EMAIL PROTECTED]> writes:
>
> > On Wed, Jun 28, 2006 at 06:31:05PM +1200, Sam Vilain wrote:
> >> Eric W. Biederman wrote:
> >> > Have a few more network interfaces for a layer 2 solution
> >> > is fundamental. B
This patch makes a needlessly global struct static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch was already sent on:
- 22 Jun 2006
--- linux-2.6.17-mm1-full/drivers/net/irda/mcs7780.c.old2006-06-22
00:38:41.0 +0200
+++ linux-2.6.17-mm1-full/drivers/net/irda/mc
jamal <[EMAIL PROTECTED]> writes:
> Andrey,
>
> On Wed, 2006-28-06 at 18:19 +0400, Andrey Savochkin wrote:
>> Hi Jamal,
>>
>> On Wed, Jun 28, 2006 at 09:53:23AM -0400, jamal wrote:
>> >
>
>>
>> Seeing guestXX-eth0 interfaces by standard tools has certain attractive
>> sides. But it creates a l
This patch contains the following possible cleanups:
- sysctl.c: the Kconfig rules already disallow CONFIG_SYSCTL=n,
there's no need for an additional check
- proper extern declarations for some variables in dccp.h
- make the following needlessly global function static:
- ipv4.c: dccp
On Wed, Jun 28, 2006 at 12:17:35PM -0400, jamal wrote:
>
> On Wed, 2006-28-06 at 18:19 +0400, Andrey Savochkin wrote:
> >
> > Seeing guestXX-eth0 interfaces by standard tools has certain attractive
> > sides. But it creates a lot of undesired side effects.
> >
>
> I apologize because i butted
Andrey Savochkin <[EMAIL PROTECTED]> writes:
> Ok, fine.
> Now I'm working on socket code.
>
> We still have a question about implicit vs explicit function parameters.
> This question becomes more important for sockets: if we want to allow to use
> sockets belonging to namespaces other than the cu
On Wednesday 28 June 2006 18:04, Larry Finger wrote:
> Michael Buesch wrote:
> >
> > It appears to be an older card. There are quite some
> > special codepaths for this, I think.
>
> Yes, I bought this card before the G specifications were finalized.
Oh, very interresting. I did not know that th
Herbert Xu wrote:
>
> Yes, however I think the same argument could be applied to TOE.
>
> With their RDMA NIC, we'll have TCP/SCTP connections that
> bypass netfilter, tc, IPsec, AF_PACKET/tcpdump and the rest
> of our stack while at the same time it is using the same IP
> address as us and deci
Herbert Poetzl <[EMAIL PROTECTED]> writes:
>> Have a few more network interfaces for a layer 2 solution
>> is fundamental. Believing without proof and after arguments
>> to the contrary that you have not contradicted that a layer 2
>> solution is inherently slower is non-productive.
>
> assumin
Andrey,
On Wed, 2006-28-06 at 18:19 +0400, Andrey Savochkin wrote:
> Hi Jamal,
>
> On Wed, Jun 28, 2006 at 09:53:23AM -0400, jamal wrote:
> >
>
> Seeing guestXX-eth0 interfaces by standard tools has certain attractive
> sides. But it creates a lot of undesired side effects.
>
I apologize be
Michael Buesch wrote:
It appears to be an older card. There are quite some
special codepaths for this, I think.
Yes, I bought this card before the G specifications were finalized.
Well, we did not want to have the card, because at this point
it did not make sense. We all have 4306 cards.
But
Herbert Poetzl <[EMAIL PROTECTED]> writes:
> On Wed, Jun 28, 2006 at 06:31:05PM +1200, Sam Vilain wrote:
>> Eric W. Biederman wrote:
>> > Have a few more network interfaces for a layer 2 solution
>> > is fundamental. Believing without proof and after arguments
>> > to the contrary that you have n
Cedric Le Goater <[EMAIL PROTECTED]> writes:
> How that proposal differs from the initial Daniel's patchset ? how far was
> that patchset to reach a similar agreement ?
My impression is as follows. The OpenVz implementation and mine work
on the same basic principles of handling the network stack
Daniel Lezcano <[EMAIL PROTECTED]> writes:
> Daniel Lezcano wrote:
>> Andrey Savochkin wrote:
>>
>>> Structures related to IPv4 rounting (FIB and routing cache)
>>> are made per-namespace.
>
> Hi Andrey,
>
> if the ressources are private to the namespace, how do you will handle NFS
> mounted befor
On Wed, 2006-06-28 at 00:07 -0700, David Miller wrote:
> Roland, there is no way in the world we would have let support for
> RDMA into the kernel tree had we seen and reviewed it on netdev. I've
> discussed this with Andrew Morton, and we'd like you to please revert
> all of the RDMA code from Li
"Serge E. Hallyn" <[EMAIL PROTECTED]> writes:
> Quoting Eric W. Biederman ([EMAIL PROTECTED]):
>> > I think we're reaching the limits of namespaces. It would be much easier
>> > with a container id in each kernel object we want to isolate.
>>
>> Nope. Except for the fact that names are peculiar
On Wed, 2006-06-28 at 15:35 +1000, Herbert Xu wrote:
> On Tue, Jun 27, 2006 at 09:43:23PM -0700, David Miller wrote:
> >
> > Socket state, and that is one thing I don't see them doing yet.
>
> I wonder what happens when the Linux TCP stack attempts to open a
> connection to a remote host when tha
On Wed, 2006-06-28 at 00:07 -0700, David Miller wrote:
> Roland, there is no way in the world we would have let support for
> RDMA into the kernel tree had we seen and reviewed it on netdev. I've
> discussed this with Andrew Morton, and we'd like you to please revert
> all of the RDMA code from Li
Dave Hansen <[EMAIL PROTECTED]> writes:
> On Wed, 2006-06-28 at 00:52 +0200, Herbert Poetzl wrote:
>> seriously, what I think Eric meant was that it
>> might be nice (especially for migration purposes)
>> to keep the device namespace completely virtualized
>> and not just isolated ...
>
> It might
On Wed, 2006-06-28 at 14:29 +1000, Herbert Xu wrote:
> On Wed, Jun 28, 2006 at 12:18:25AM -0400, Jeff Garzik wrote:
> >
> > A PCI device that presents itself as a SCSI controller, but under the
> > hood is really iSCSI-over-TCP smells like TOE. Running a virtualized
> > Linux guest on top of a
jamal <[EMAIL PROTECTED]> writes:
> On Wed, 2006-28-06 at 15:36 +0200, Herbert Poetzl wrote:
>
>> note: personally I'm absolutely not against virtualizing
>> the device names so that each guest can have a separate
>> name space for devices, but there should be a way to
>> 'see' _and_ 'identify' th
Daniel,
On Wed, Jun 28, 2006 at 03:51:32PM +0200, Daniel Lezcano wrote:
> Daniel Lezcano wrote:
> > Andrey Savochkin wrote:
> >
> >> Structures related to IPv4 rounting (FIB and routing cache)
> >> are made per-namespace.
>
> Hi Andrey,
>
> if the ressources are private to the namespace, how do
On Fri, Jun 23, 2006 at 02:32:12PM -0700, Don Fry wrote:
> This set of changes combines the work done by Len Sorensen and myself to
> add compile time support for NAPI for the pcnet32 driver. I have tested
> it on ia32 and ppc64 hardware with various versions of the pcnet32
> adapter. I have also
On Tuesday 27 June 2006 22:37, Larry Finger wrote:
> Michael Buesch wrote:
> > On Tuesday 27 June 2006 22:06, Larry Finger wrote:
> >> John,
> >>
> >> I would like to find a diplomatic solution to this impasse between Michael
> >> and Jeff, which is why
> >> I'm writing to you privately. Michael
Structures related to IPv4 rounting (FIB and routing cache)
are made per-namespace.
Hi Andrey,
if the ressources are private to the namespace, how do you will handle
NFS mounted before creating the network namespace ? Do you take care of
that or simply assume you can't access NFS anymore ?
On Wed, 2006-06-28 at 15:35 +1000, Herbert Xu wrote:
> On Tue, Jun 27, 2006 at 09:43:23PM -0700, David Miller wrote:
> >
> > Socket state, and that is one thing I don't see them doing yet.
>
> I wonder what happens when the Linux TCP stack attempts to open a
> connection to a remote host when tha
On Wed, Jun 28, 2006 at 06:31:05PM +1200, Sam Vilain wrote:
> Eric W. Biederman wrote:
> > Have a few more network interfaces for a layer 2 solution
> > is fundamental. Believing without proof and after arguments
> > to the contrary that you have not contradicted that a layer 2
> > solution is inh
On Wed, Jun 28, 2006 at 03:51:32PM +0200, Daniel Lezcano wrote:
> Daniel Lezcano wrote:
> >Andrey Savochkin wrote:
> >
> >>Structures related to IPv4 rounting (FIB and routing cache)
> >>are made per-namespace.
>
> Hi Andrey,
>
> if the ressources are private to the namespace, how do you will
>
Herbert Poetzl <[EMAIL PROTECTED]> writes:
> last time I pointed to such 'misguided' apps which
> made assumptions that are not necessarily true
> inside a virtual environment (e.g. pstree, initpid)
> the general? position was that those apps should
> be fixed instead adding a 'workaround'
I agr
Hi Jamal,
On Wed, Jun 28, 2006 at 09:53:23AM -0400, jamal wrote:
>
> On Wed, 2006-28-06 at 15:36 +0200, Herbert Poetzl wrote:
>
> > note: personally I'm absolutely not against virtualizing
> > the device names so that each guest can have a separate
> > name space for devices, but there should be
On Wed, 2006-06-28 at 00:18 -0400, Jeff Garzik wrote:
> Herbert Xu wrote:
> > On Tue, Jun 27, 2006 at 11:24:25PM -0400, Jeff Garzik wrote:
> >> I don't see how that position has changed?
> >>
> >> http://linux-net.osdl.org/index.php/TOE
> >
> > Well I must say that RDMA over TCP smells very much l
Quoting Eric W. Biederman ([EMAIL PROTECTED]):
> > I think we're reaching the limits of namespaces. It would be much easier
> > with a container id in each kernel object we want to isolate.
>
> Nope. Except for the fact that names are peculiar (sockets, network
> device names, IP address, routes.
On Tue, Jun 27, 2006 at 10:07:29PM -0600, Eric W. Biederman wrote:
> Herbert Poetzl <[EMAIL PROTECTED]> writes:
>
> > On Tue, Jun 27, 2006 at 10:29:39AM -0600, Eric W. Biederman wrote:
> >> Herbert Poetzl <[EMAIL PROTECTED]> writes:
> >
> >> I watched the linux-vserver irc channel for a while and
Daniel Lezcano wrote:
Andrey Savochkin wrote:
Structures related to IPv4 rounting (FIB and routing cache)
are made per-namespace.
Hi Andrey,
if the ressources are private to the namespace, how do you will handle
NFS mounted before creating the network namespace ? Do you take care of
that o
Cedric Le Goater <[EMAIL PROTECTED]> writes:
> Eric W. Biederman wrote:
>
>> Despite what it might look like unix domain sockets do not live in the
>> filesystem. They store a cookie in the filesystem that roughly
>> corresponds to the port number of an AF_INET socket. When you open a
>> socket
On Wed, 28 Jun 2006, Catherine Zhang wrote:
> Hi,
>
> Minor fix (un-export selinux_get_sock_sid()).
Thanks, looks ok to me.
Acked-by: James Morris <[EMAIL PROTECTED]>
--
James Morris
<[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a mes
On Wed, 2006-28-06 at 15:36 +0200, Herbert Poetzl wrote:
> note: personally I'm absolutely not against virtualizing
> the device names so that each guest can have a separate
> name space for devices, but there should be a way to
> 'see' _and_ 'identify' the interfaces from outside
> (i.e. host or
On Wed, 2006-28-06 at 15:01 +0200, Thomas Graf wrote:
> * jamal <[EMAIL PROTECTED]> 2006-06-28 08:22
[..]
> > Note, in such a case: iflink rewriting will do it just fine
> > but then you loose the original info (I think it would be good to not
> > loose such info to know the origin). I dont know if
please consider for 2.6.18 -- thanks!
[ATM]: [idt77105] should be __devinit not __init
Signed-off-by: Chas Williams <[EMAIL PROTECTED]>
---
commit 51403ade3cedfc85f1f41d81cb3a227f9ce2366f
tree f9cf0143466de92eda0080e27240d4b53c130c18
parent 982703b5b38b314081d79ebc657fc06b1b6fe6b6
author chas wi
please consider for 2.6.18 -- thanks!
[ATM]: basic sysfs support for ATM devices
From: Roman Kagan <[EMAIL PROTECTED]>
Signed-off-by: Chas Williams <[EMAIL PROTECTED]>
---
commit 034e4008acda89bc2422541e077f2dbfd530b717
tree e528e0e6f2d69c729f2daf6618df22133b3e4818
parent 4768199f3a5582378164820
please consider for 2.6.18 -- thanks!
[ATM]: [suni] change suni_init to __devinit
Signed-off-by: Chas Williams <[EMAIL PROTECTED]>
---
commit 4768199f3a5582378164820cc74251e485a01292
tree fd27293baebffd029ae53a6efe18913cfb68cada
parent 3d63ef0340a7f49a72f5eaa33f08b38fa78d48e1
author chas william
please consider for 2.6.18 -- thanks!
[ATM]: [iphase] should be __devinit not __init
Signed-off-by: Chas Williams <[EMAIL PROTECTED]>
---
commit a6d3f9a19cc29d6ece38f057eb896c16a4372129
tree 109e40a1fb873f0105bb75ecf21456f25b1756ef
parent 51403ade3cedfc85f1f41d81cb3a227f9ce2366f
author chas will
On Tue, Jun 27, 2006 at 09:38:14PM -0600, Eric W. Biederman wrote:
> Alexey Kuznetsov <[EMAIL PROTECTED]> writes:
>
> > Hello!
> >
> >> It may look weird, but do application really *need* to see eth0 rather
> >> than eth858354?
> >
> > Applications do not care, humans do. :-)
> >
> > What's about
* jamal <[EMAIL PROTECTED]> 2006-06-28 08:22
> Let me see if i understood correctly:
> you have a device from both vlan1 and vlan2 both being redirected to
> ifb1? and vlan 3, 4=> ifb2?
> And i take it to make it interesting vlan1,2 on eth0 and vlan3,4 ontop
> of eth1? note the iflink would/should
On Wed, 2006-28-06 at 12:18 +0200, Thomas Graf wrote:
> * jamal <[EMAIL PROTECTED]> 2006-06-27 09:07
[..]
> > Note the meta-setter (been sitting on it for too long) also set the
> > input_dev.
>
> Could you share that piece of code so I don't have to duplicate
> that effort?
>
I will look it up
From: Allan Stephens <[EMAIL PROTECTED]>
Now determines tailroom of bundle buffer by directly inspection of buffer.
Previously, buffer was assumed to have a max capacity equal to the link MTU,
but the addition of link MTU negotiation means that the link MTU can increase
after the bundle buffer is
This patch set includes three fixes/cleanups. Please see each individual
patch for further description.
Please pull from:
git://tipc.cslab.ericsson.net/pub/git/tipc.git
(rebased on linux/kernel/git/davem/net-2.6.git)
Summary:
net/tipc/core.c |3 ++-
net/tipc/link.c | 11 ++-
From: Allan Stephens <[EMAIL PROTECTED]>
Signed-off-by: Allan Stephens <[EMAIL PROTECTED]>
Signed-off-by: Per Liden <[EMAIL PROTECTED]>
---
net/tipc/core.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/net/tipc/core.c b/net/tipc/core.c
index 5003acb..0539a83 100644
--
From: Allan Stephens <[EMAIL PROTECTED]>
Now allocates reply space for "get links" request based on number of actual
links, not number of potential links. Also, limits reply to "get links" and
"get nodes" requests to 32KB to match capabilities of tipc-config utility
that issued request.
Signed-o
Hi Eric,
On Tue, Jun 27, 2006 at 10:20:32PM -0600, Eric W. Biederman wrote:
> Andrey Savochkin <[EMAIL PROTECTED]> writes:
[snip]
> > My first patchset covers devices but not sockets.
> > The only difference from what you're suggesting is ipv4 routing.
> > For me, it is not less important than dev
Hello,
Eric W. Biederman wrote:
> Thinking about this I am going to suggest a slightly different direction
> for get a patchset we can merge.
>
> First we concentrate on the fundamentals.
> - How we mark a device as belonging to a specific network namespace.
> - How we mark a socket as belonging
1 - 100 of 108 matches
Mail list logo
