Hi,
On Tue, 24 Apr 2012, 17:40-, Li, Qing wrote:
Yup, all good points. In fact we have considered all of these while doing
the work. In case you haven't seen it already, we did write about these
issues in our paper and how we tried to address those, flow-table was one
of the solutions.
On Wed, Apr 25, 2012 at 01:22:06PM +0400, Maxim Konovalov wrote:
Hi,
On Tue, 24 Apr 2012, 17:40-, Li, Qing wrote:
Yup, all good points. In fact we have considered all of these while doing
the work. In case you haven't seen it already, we did write about these
issues in our paper
Because there were leaks, there were 100% panics for IPv6, ... at least on
the version I had seen in autumn last year.
There is certainly no one more interested then me on these in, esp. for v6
where the removal of route caching a long time ago made nd6_nud_hint() a NOP
with dst and rt being
On Tue, Apr 17, 2012 at 12:34:20PM -0700, Jason Evans wrote:
As a result of the recent jemalloc update, the format for
/etc/malloc.conf has changed. If your system has an old-style
/etc/malloc.conf, you will want to delete it prior to
installworld, and optionally re-create it using the new
On Apr 25, 2012, at 9:39 AM, Ruslan Ermilov wrote:
So you removed _malloc_options that was part of the documented
programming API, while some software made use of it.
While removing part of the documented API was definitely a bad
idea, you didn't provide any mean to detect this change
Hi,
Applications using ASYNC transfers needs to be re-compiled in 10-current after
this change:
http://svn.freebsd.org/changeset/base/234684
This change will _not_ be backported to 9-stable or 8-stable.
--HPS
___
freebsd-current@freebsd.org mailing
On Wed, Apr 25, 2012 at 08:03:24PM +0200, Hans Petter Selasky wrote:
Hi,
Applications using ASYNC transfers needs to be re-compiled in 10-current
after
this change:
http://svn.freebsd.org/changeset/base/234684
This change will _not_ be backported to 9-stable or 8-stable.
You need to
On 25. Apr 2012, at 15:45 , K. Macy wrote:
a) Where is the possible leak in the legacy path?
It's been somewhere in ip_output() in one of the possible combinations
go through the code flow. I'd probably need to apply a patch to a tree
to get there again. It's been more than 6 months for me as
On 2012-04-24 21:49, Jean-Sébastien Pédron wrote:
Hi everyone,
vfscanf(3) in HEAD (r234606) segfaults when compiled with clang. For
instance, here is a call made in cmake which crashes:
fscanf(f, %*[^\n]\n);
Using r234549 here, everything compiled with clang, but I cannot make
that
25.04.2012 22:57, Dimitry Andric пишет:
On 2012-04-24 21:49, Jean-Sébastien Pédron wrote:
Hi everyone,
vfscanf(3) in HEAD (r234606) segfaults when compiled with clang. For
instance, here is a call made in cmake which crashes:
fscanf(f, %*[^\n]\n);
Using r234549 here, everything
On 2012-04-25 21:13, Boris Samorodov wrote:
25.04.2012 22:57, Dimitry Andric пишет:
On 2012-04-24 21:49, Jean-Sébastien Pédron wrote:
Hi everyone,
vfscanf(3) in HEAD (r234606) segfaults when compiled with clang. For
instance, here is a call made in cmake which crashes:
fscanf(f,
Hi,
On Sat, Apr 21, 2012 at 4:19 AM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Apr 18, 2012 at 2:22 AM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Mon, Apr 16, 2012 at 5:50 PM, Arnaud Lacombe lacom...@gmail.com wrote:
[...]
I reproduced the previous problem on 10-CURRENT
On Mon, Apr 23, 2012 at 1:16 AM, Ganael LAPLANCHE marty...@freebsd.org wrote:
On Fri, 20 Apr 2012 08:14:17 +0200, Lars Engels wrote
Hi everyone,
This is the same for my x200, but you can make it work:
On 9.0-RELEASE you have to configure through device.hints(5),
in CURRENT you can
On (23/04/2012 08:16), Ganael LAPLANCHE wrote:
On Fri, 20 Apr 2012 08:14:17 +0200, Lars Engels wrote
Hi everyone,
This is the same for my x200, but you can make it work:
On 9.0-RELEASE you have to configure through device.hints(5),
in CURRENT you can configure it on thy fly. See
On Apr 25, 2012, at 10:43 AM, Jason Evans wrote:
On a related note, is there any way to find all ports that refer to
_malloc_options without extracting source for all of them? I considered
being proactive about finding software that depends on _malloc_options, but
no tractable
On Wed, Apr 25, 2012 at 09:37:36PM -0700, Tim Kientzle wrote:
The Ports maintainers will run experimental ports builds on the
port build clusters to help verify potentially disruptive changes
like this before they are committed.
Well, actually, portmgr@. Send a PR with [exp-run] in the
16 matches
Mail list logo
