[Bug 664778] [souphttpsrc] chunk allocator: memory waste

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Mon Dec 5 02:31:27 PST 2011


https://bugzilla.gnome.org/show_bug.cgi?id=664778
  GStreamer | gst-plugins-good | unspecified

--- Comment #10 from René Stadler <mail at renestadler.de> 2011-12-05 10:31:25 UTC ---
(In reply to comment #9)
> How about deploy FIONREAD ioctl?
> Through this syscall, we can guess how many “unread” data is remained in the
> TCP socket.
> Please refer the kernel code at /net/ipv4/tcp.c tcp_ioctl()
> As a result we can eliminate "zero read" case which cause malloc() / free()
> overhead.

Yes, but this has to be used at the libsoup level.

> Regarding question #3,
> What I really mean was
> What will be happen if I delete chunk_allocator.
> just worry about the unexpected malfunction in last revision.

As far as I can see, there is no commit you can just revert (the allocator
stuff was added a very long time ago). So you have to modify the element
yourself, which is of course possible. As Tim pointed out, the pad_alloc path
won't provide a performance gain, so you should be able to remove it as a quick
fix.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list