On Jan 9, 2010, at 1:31 PM, Jeff Squyres wrote:
>>> Mmm, couldn't that information (I guess you mean the "Definitions",
>>> "Hwloc Objects" and "Hwloc Indexes") be moved to another, common hwloc.1
>>> page?
>>
>> I'm also realizing that these should also be in the PDF/html
>> documentation. This
Jeff Squyres, le Mon 11 Jan 2010 09:48:14 -0500, a écrit :
> If we keep them separate, I think I'd be in favor of splitting much of the
> top of hwloc-bind.1in off into hwloc.1in and having each of the tool man
> pages refer to it.
That was my plan.
The idea is that while the PDF has general pr
Been mulling this for a few days; here's my thoughts...
On Jan 7, 2010, at 1:35 PM, Samuel Thibault wrote:
> Considering future network topology support, I believe we probably need
> to fix a couple of things before releasing 1.0. Just to sum up the a
> bunch of points that have been raised in
On Jan 11, 2010, at 9:59 AM, Samuel Thibault wrote:
> > If we keep them separate, I think I'd be in favor of splitting much of the
> > top of hwloc-bind.1in off into hwloc.1in and having each of the tool man
> > pages refer to it.
>
> That was my plan.
K; I can do that.
> The idea is that whi
Jeff Squyres, le Mon 11 Jan 2010 10:12:00 -0500, a écrit :
> Been mulling this for a few days; here's my thoughts...
Thanks!
> Are you thinking of adding bandwidth attributes?
When the information is available through some way (be it by hand), yes.
> Or are you thinking of adding weighting betw
Jeff Squyres, le Mon 11 Jan 2010 10:12:45 -0500, a écrit :
> > The idea is that while the PDF has general principles, the details of
> > the vocabulary & such looks like a manpage and is useful to have in a
> > manpage. Having it as a real manpages is convenient when using man tools
> > that can qu
On Jan 11, 2010, at 11:15 AM, Samuel Thibault wrote:
> > For extra bonus points, I'll have the PDF refer to hwloc.1. :-)
>
> Mmm, maybe that wasn't exactly my plan: it was that hwloc.1 would
FWIW, it's actually hwloc.7 (realized that section 7 was more appropriate after
I was typing it up).
>
Jeff Squyres, le Mon 11 Jan 2010 11:31:12 -0500, a écrit :
> That's what I was trying to say in my first mail -- the text that is now
> hwloc.7in overlaps what is currently in hwloc.doxy (*some* text overlaps;
> some does not). I.e., hwloc.7in and hwloc.doxy intersect; one is not a
> subset of
On Jan 11, 2010, at 11:12 AM, Samuel Thibault wrote:
> > Are you thinking of adding bandwidth attributes?
>
> When the information is available through some way (be it by hand), yes.
>
> > Or are you thinking of adding weighting between objects in the hierarchy?
> > Or ...?
>
> I'd tend to th
Jeff Squyres, le Mon 11 Jan 2010 14:21:53 -0500, a écrit :
> On Jan 11, 2010, at 11:12 AM, Samuel Thibault wrote:
> > I once thought about adding gpuset, maybe, but since the kinds of
> > objects will probably vary a lot, maybe it's better to not try to be
> > smart and let layers above handle it,
On Jan 11, 2010, at 2:52 PM, Samuel Thibault wrote:
> > Maybe it would be better to add a (void*) on to the object to allow
> > arbitrary 3rd parties to cache information off any given hwloc object.
>
> I.e. the userdata pointer in the hwloc_obj_t structure?
Ummm... right. :-)
(I really need
Jeff Squyres, le Mon 11 Jan 2010 15:20:45 -0500, a écrit :
> > > I'm curious -- what's the definition of cat'ing 2 XML files together?
> > > Does the 2nd become a subtree of the first?
> >
> > No, I mean putting both under a "misc" object for instance.
>
> Can you explain more; maybe provide an
Samuel Thibault, le Mon 11 Jan 2010 21:27:35 +0100, a écrit :
> Jeff Squyres, le Mon 11 Jan 2010 15:20:45 -0500, a écrit :
> > > > I'm curious -- what's the definition of cat'ing 2 XML files together?
> > > > Does the 2nd become a subtree of the first?
> > >
> > > No, I mean putting both under a
On Jan 11, 2010, at 3:27 PM, Samuel Thibault wrote:
> The concatenation would be
>
>
>
>
>
>dmi_board_vendor="" dmi_board_name="" memory_kB="0" huge_page_free="0"
> huge_page_size_kB="0">
>
>
>dmi_board_vendor="" dmi_board_name="" memory_kB="0" huge_page_free="0"
> huge_pag
Jeff Squyres, le Mon 11 Jan 2010 15:54:55 -0500, a écrit :
> cat a.xml b.xml > c.xml
>
> and then using c.xml directly (which I didn't see how that would work).
> Instead, you're talking about manually stitching multiple XML files together
> under a single , further enclosed under a single "Mis
Jeff Squyres wrote:
> I don't think we should let doxygen dictate the code that we write.
Agreed. Headers are already kind of the horrible :)
> 1. make doxy do what we want
>
Setting SHORT_NAMES to YES in doxygen.cfg seems to help. html and latex
filenames are replaced with things like a00026
Brice Goglin, le Mon 11 Jan 2010 23:50:43 +0100, a écrit :
> Anyway, if we're going to drop latex files before building the tarball,
> maybe we can drop manpages that are not in $(man3_MANS) too?
Agree, we don't need to install them anyway, and it saves room too :)
Samuel
Creating nightly hwloc snapshot SVN tarball was a success.
Snapshot: hwloc 1.0a1r1595
Start time: Mon Jan 11 21:01:04 EST 2010
End time: Mon Jan 11 21:03:11 EST 2010
Your friendly daemon,
Cyrador
18 matches
Mail list logo
