Displaying 6 results from an estimated 6 matches for "360593".
Did you mean:
360592
2011 Jan 31
1
Question on ploting multiple series on the same plot
Thanks in advance for all help ,
I just started using R and have already done the following.
1. Read through multiple files to get input data
2. plot a vector (X say)
3. end
Now i want to plot the vector X for different files on the same plot, and I
don't know how to do that.
One option I considered was to have a global data frame that holds X for
each file.
and then plot after iterating
2015 Jan 06
2
[PATCH nouveau 09/11] drm: export some variable and functions to resue the PM functions
On Tue, Jan 06, 2015 at 09:44:01AM -0500, Ilia Mirkin wrote:
> On Tue, Jan 6, 2015 at 9:37 AM, Thierry Reding <thierry.reding at gmail.com> wrote:
> > On Tue, Jan 06, 2015 at 08:27:06PM +0800, Vince Hsu wrote:
> >>
> >> On 01/06/2015 07:49 PM, Thierry Reding wrote:
> >> >* PGP Signed by an unknown key
> >> >
> >> >On Mon, Jan 05,
2015 Jan 06
0
[PATCH nouveau 09/11] drm: export some variable and functions to resue the PM functions
...9;t actually end up using any of
it. (And even if you did, it'd be just one of the firmware files, not
all of them).
Here was the patch: http://permalink.gmane.org/gmane.comp.video.dri.devel/102457
Looks like nvc0 only was:
NVC0: 878726 bytes
text data bss dec hex filename
360593 140327 80 501000 7a508 drivers/gpu/drm/nouveau/nouveau.ko
compared to the combo package:
NV04 + NV50 + NVC0: 1343482 bytes
text data bss dec hex filename
579171 184264 480 763915 ba80b drivers/gpu/drm/nouveau/nouveau.ko
-ilia
2013 Feb 27
1
Slow read performance
Help please-
I am running 3.3.1 on Centos using a 10GB network. I get reasonable write speeds, although I think they could be faster. But my read speeds are REALLY slow.
Executive summary:
On gluster client-
Writes average about 700-800MB/s
Reads average about 70-80MB/s
On server-
Writes average about 1-1.5GB/s
Reads average about 2-3GB/s
Any thoughts?
Here are some additional details:
2014 Mar 23
0
[PATCH] drm/nouveau: allow nv04/nv50/nvc0+ parts of the driver to be separated
...x filename
333755 35094 160 369009 5a171 drivers/gpu/drm/nouveau/nouveau.ko
NV50: 722079 bytes
text data bss dec hex filename
346476 34727 480 381683 5d2f3 drivers/gpu/drm/nouveau/nouveau.ko
NVC0: 878726 bytes
text data bss dec hex filename
360593 140327 80 501000 7a508 drivers/gpu/drm/nouveau/nouveau.ko
NV04 + NV50: 995817 bytes
text data bss dec hex filename
472244 59528 480 532252 81f1c drivers/gpu/drm/nouveau/nouveau.ko
NV04 + NVC0: 1167727 bytes
text data bss dec hex filename
493...
2014 Feb 15
3
[RFC PATCH] drm/nouveau: split off nvc0 compilation
So... I was wondering what the impact of splitting up the card compilation by
e.g. generation would be. Depending on the split things would get fairly
intertwined, so I thought I'd start small. This just splits NVC0 from
everything else. I figure that for the people this matters the most to, NVC0
is the least relevant card -- people with sub-1GB of RAM, older hardware.
With my config options