It is interesting that how a thread goes off topic!
Anyway, I will appreciate if folks, especially Jack, provide
a firm comment on the original question: Does intel chips (specifically 82576)
support IP TX checksum offload? If so, why the driver does not support it?
On 9/19/2011 8:59 AM, Jack V
on 19/09/2011 01:25 Gleb Kurtsou said the following:
> Let me share my experience as well.
>
> My repo: https://github.com/glk/freebsd-head/
>
> I used rebase to keep local branches as well, but no longer do so. Such
> setup worked for me at least for two years, I had local changes and
> worked
on 19/09/2011 10:41 Andriy Gapon said the following:
> on 19/09/2011 01:25 Gleb Kurtsou said the following:
>> Let me share my experience as well.
>>
>> My repo: https://github.com/glk/freebsd-head/
>>
>> I used rebase to keep local branches as well, but no longer do so. Such
>> setup worked for m
Arnaud (and others),
Liaising with vendors is not an easy task. The reason why Intel (and
other vendors) don't supply detailed history and reasoning for their
development efforts is that their engineers are likely tasked with
"making it work" versus "writing lots of stuff down for public
release."
On Sun, Sep 18, 2011 at 7:48 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Sun, Sep 18, 2011 at 10:01 PM, Luigi Rizzo wrote:
> > On Sun, Sep 18, 2011 at 06:05:33PM -0400, Arnaud Lacombe wrote:
> >> Hi,
> >>
> >> On Sun, Sep 18, 2011 at 5:06 PM, Luigi Rizzo
> wrote:
> >> > On Sun, Sep 18, 2011 at 03:19
On Sunday, September 18, 2011 10:48:32 pm Arnaud Lacombe wrote:
> As the PCI spec is not public, I've not been able to find out from the
> few public datasheet how the PCI MSI-X capability field is first
> programmed. I'd assume that the BIOS is using the data in the NVM to
> program it at power up
On Sunday, September 18, 2011 5:45:26 pm Richard Yao wrote:
> Dear Jilles,
>
> I am using sigwaitinfo() with all interrupts masked to avoid the
> possibility of race conditions in signal handlers, but I have not used
> any realtime signals. Linux 2.6.35 found a way to invoke the SIGIO
> handler de
If the value lags next by one then it is ours. This rule applies to
all callers so the rule holds consistently.
On Mon, Sep 19, 2011 at 5:53 AM, Arnaud Lacombe wrote:
> Hi,
>
> On Fri, Sep 16, 2011 at 10:41 AM, K. Macy wrote:
>> On Fri, Sep 16, 2011 at 3:02 AM, Arnaud Lacombe wrote:
>>> Hi,
>>>
Hi Daniel,
Thank you for the information. I agree with your comment below.
" But if you're simply running the ftp client on an otherwise idle host,
and two subsequent bind() calls get assigned the same 'random' port,
I'd say the port randomization is not working properly :)"
Does anyone have any
Hi,
On Mon, Sep 19, 2011 at 5:28 AM, Adrian Chadd wrote:
> Arnaud (and others),
>
> Liaising with vendors is not an easy task. The reason why Intel (and
> other vendors) don't supply detailed history and reasoning for their
> development efforts is that their engineers are likely tasked with
> "m
Thanks
On 2011-09-16 23:14, Julian Elischer wrote:
On 9/16/11 1:30 PM, Charlie Martin wrote:
I need to add some custom static dtrace probes in 7.2 apps; the
online documentation refers only to 9 however. Can someone tell me
how to replace what's done in bsd.dtrace.mk for 7.2?
I' am not sure
Dude, you say that like it was an option.
On 2011-09-16 18:46, Matthias Andree wrote:
Am Freitag, den 16.09.2011, 14:30 -0600 schrieb Charlie Martin:
I need to add some custom static dtrace probes in 7.2 apps; the online
documentation refers only to 9 however. Can someone tell me how to
replac
>>> The data sheet for intel 82576 advertises IP TX/RX checksum offload
>>> but the driver does not set CSUM_IP in ifp->if_hwassist. Does this mean
>>> that driver (and chip) do not support IP TX checksum offload or the
>>> support for TX is not yet included in the driver?
>>
>> The first question
On 9/19/11 9:17 AM, Charlie Martin wrote:
Dude, you say that like it was an option.
It's understood about the realities of commercial decisions, however,
if you really want to trace APPS
that means user space dtrace and 7.2 just doesn't have the hooks to
do non-kernel dtrace.
As a side not
On 2011-09-19 10:38, Julian Elischer wrote:
On 9/19/11 9:17 AM, Charlie Martin wrote:
Dude, you say that like it was an option.
It's understood about the realities of commercial decisions, however,
if you really want to trace APPS
that means user space dtrace and 7.2 just doesn't have the
On Mon, Sep 19, 2011 at 10:17:22AM -0400, Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Sep 19, 2011 at 5:28 AM, Adrian Chadd wrote:
> > Arnaud (and others),
> >
> > Liaising with vendors is not an easy task. The reason why Intel (and
> > other vendors) don't supply detailed history and reasoning for t
Hi,
On Mon, Sep 19, 2011 at 12:59 PM, YongHyeon PYUN wrote:
> On Mon, Sep 19, 2011 at 10:17:22AM -0400, Arnaud Lacombe wrote:
>> Hi,
>>
>> On Mon, Sep 19, 2011 at 5:28 AM, Adrian Chadd wrote:
>> > Arnaud (and others),
>> >
>> > Liaising with vendors is not an easy task. The reason why Intel (and
Hi,
[adding Fabien Thomas to the CC: list]
On Sun, Sep 18, 2011 at 5:14 AM, Andriy Gapon wrote:
>
> Just decided to follow the global trends and trying to throw all of my
> local/private changes at you in hope that the "crowd-sourcing magic" might
> somehow happen :-) This seems definitely easi
18 matches
Mail list logo
