On 11/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
I have a patch that I got from the mailing list. But it does not contain
the changes that adds tso_segsz to mbuffer header structure.
Can any one please send me the latest patch for TSO that contains stack
changes?
Thanks,
~Siva
:[EMAIL PROTECTED] On Behalf Of Jack Vogel
Sent: Wednesday, September 06, 2006 3:53 AM
To: Andre Oppermann
Cc: freebsd-net; freebsd-current
Subject: Re: RFC: TSO patch for current
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
> Jack Vogel wrote:
> > On 9/5/06, Andre Op
Oppermann
Cc: freebsd-net; freebsd-current
Subject: Re: RFC: TSO patch for current
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
> Jack Vogel wrote:
> > On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
> >> Prafulla Deuskar wrote:
> >> >
Prafulla Deuskar wrote:
> Pyun YongHyeon [EMAIL PROTECTED] wrote:
> >What happen if users disable hardware
> > VLAN tag insertion with ifconfig(8)?
>
> TSO requires that VLAN tag insertion is done by hardware
This is bad news.
I use CARP interfaces in all my VLANs which places the interface
in p
Pyun YongHyeon [EMAIL PROTECTED] wrote:
> On Fri, Sep 01, 2006 at 03:51:21PM -0700, Jack Vogel wrote:
> > This is a patch for the stack and the em driver to enable TSO
> > on CURRENT. Previously I had problems getting it to work, but
> > this is functional.
> >
> > I should note that CURRENT
Ian FREISLICH wrote:
Andre Oppermann wrote:
Jack Vogel wrote:
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
If you do the ifconfig changes there will need to be a small amount of
code added to em_ioctl() but it should be trivial.
You want me to reissue a driver patch with changes f
Ian FREISLICH wrote:
Andre Oppermann wrote:
Jack Vogel wrote:
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
If you do the ifconfig changes there will need to be a small amount of
code added to em_ioctl() but it should be trivial.
You want me to reissue a driver patch with changes f
Andre Oppermann wrote:
> Jack Vogel wrote:
> > On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
> >> > If you do the ifconfig changes there will need to be a small amount of
> >> > code added to em_ioctl() but it should be trivial.
> >> >
> >> > You want me to reissue a driver patch with chang
Jack Vogel wrote:
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
> If you do the ifconfig changes there will need to be a small amount of
> code added to em_ioctl() but it should be trivial.
>
> You want me to reissue a driver patch with changes for your code?
Yes, please do so. I've go
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
Jack Vogel wrote:
> On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
>> Prafulla Deuskar wrote:
>> > Your patch looks good and is the way to go.
>> >
>> > So after Jack confirms that your patch works with the em driver
>> > would you comm
Jack Vogel wrote:
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
Prafulla Deuskar wrote:
> Your patch looks good and is the way to go.
>
> So after Jack confirms that your patch works with the em driver
> would you commit to to -current?
Absolutely. :-)
> The driver related changes can
On 9/5/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
Prafulla Deuskar wrote:
> Andre Oppermann [EMAIL PROTECTED] wrote:
>> Prafulla Deuskar wrote:
>>> Jack Vogel [EMAIL PROTECTED] wrote:
>>>
On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
> I can't comment on the em part
Prafulla Deuskar wrote:
Andre Oppermann [EMAIL PROTECTED] wrote:
Prafulla Deuskar wrote:
Jack Vogel [EMAIL PROTECTED] wrote:
On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
I can't comment on the em part but the tcp_output.c stuff looks
very much like a straight port from NetBSD. If
Andre Oppermann [EMAIL PROTECTED] wrote:
> Prafulla Deuskar wrote:
> >Jack Vogel [EMAIL PROTECTED] wrote:
> >
> >>On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>>I can't comment on the em part but the tcp_output.c stuff looks
> >>>very much like a straight port from NetBSD. If
Prafulla Deuskar wrote:
Jack Vogel [EMAIL PROTECTED] wrote:
On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
I can't comment on the em part but the tcp_output.c stuff looks
very much like a straight port from NetBSD. If we take code from
the other BSDs we have to remark this in the ema
On 9/5/06, Prafulla Deuskar <[EMAIL PROTECTED]> wrote:
Jack Vogel [EMAIL PROTECTED] wrote:
> On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
>
> >I can't comment on the em part but the tcp_output.c stuff looks
> >very much like a straight port from NetBSD. If we take code from
> >the other
Jack Vogel [EMAIL PROTECTED] wrote:
> On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
>
> >I can't comment on the em part but the tcp_output.c stuff looks
> >very much like a straight port from NetBSD. If we take code from
> >the other BSDs we have to remark this in the emails we send with
On 9/4/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
Robert Watson wrote:
> On Fri, 1 Sep 2006, Jack Vogel wrote:
>
>> This is a patch for the stack and the em driver to enable TSO on
>> CURRENT. Previously I had problems getting it to work, but this is
>> functional.
>>
>> I should note that CU
Robert Watson wrote:
On Fri, 1 Sep 2006, Jack Vogel wrote:
This is a patch for the stack and the em driver to enable TSO on
CURRENT. Previously I had problems getting it to work, but this is
functional.
I should note that CURRENT is being a pain right now, when I comment
out em in the confi
On Fri, Sep 01, 2006 at 03:51:21PM -0700, Jack Vogel wrote:
> This is a patch for the stack and the em driver to enable TSO
> on CURRENT. Previously I had problems getting it to work, but
> this is functional.
>
> I should note that CURRENT is being a pain right now, when
> I comment out em
Jack Vogel wrote:
On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
Jack Vogel wrote:
> This is a patch for the stack and the em driver to enable TSO
> on CURRENT. Previously I had problems getting it to work, but
> this is functional.
>
> I should note that CURRENT is being a pain right now
On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
I can't comment on the em part but the tcp_output.c stuff looks
very much like a straight port from NetBSD. If we take code from
the other BSDs we have to remark this in the emails we send with
patches and the commit message (otherwise we ge
On 9/2/06, Andre Oppermann <[EMAIL PROTECTED]> wrote:
Jack Vogel wrote:
> This is a patch for the stack and the em driver to enable TSO
> on CURRENT. Previously I had problems getting it to work, but
> this is functional.
>
> I should note that CURRENT is being a pain right now, when
> I comment
Jack Vogel wrote:
This is a patch for the stack and the em driver to enable TSO
on CURRENT. Previously I had problems getting it to work, but
this is functional.
I should note that CURRENT is being a pain right now, when
I comment out em in the config the kernel panics coming up,
so I had to sub
On Fri, 1 Sep 2006, Jack Vogel wrote:
This is a patch for the stack and the em driver to enable TSO on CURRENT.
Previously I had problems getting it to work, but this is functional.
I should note that CURRENT is being a pain right now, when I comment out em
in the config the kernel panics com
At Fri, 1 Sep 2006 15:51:21 -0700,
Jack Vogel wrote:
>
> This is a patch for the stack and the em driver to enable TSO
> on CURRENT. Previously I had problems getting it to work, but
> this is functional.
>
> I should note that CURRENT is being a pain right now, when
> I comment out em in the con
This is a patch for the stack and the em driver to enable TSO
on CURRENT. Previously I had problems getting it to work, but
this is functional.
I should note that CURRENT is being a pain right now, when
I comment out em in the config the kernel panics coming up,
so I had to substitute this code i
27 matches
Mail list logo
