Hmm ... a "spork" ...
http://www.theregister.co.uk/2010/08/03/illumos_opensolaris_spork/ ...
I like it, I'm glad because it means there is a better looking future after
build 134.
At the end of the day I'd love it if Oracle just started talking and carried on
developing the project as a commun
,
- jonathan
------
Jonathan Adams, Sun Microsystems, ZFS Teamhttp://blogs.sun.com/jwadams
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Cheers,
- jonathan
Thanks
Aswathi
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
--
Jonathan Adams, Sun Microsystems ZFS Team http://blogs.sun.com
usr/sfw/bin/gcc.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
which would prevent memory from being
returned to the common pool once it was used for that cache.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
e know what this process does, and if I really need it?
>
> ciao, erich
>
>
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
--
Jonathan Adams, Solaris Ker
CPU bound.
You should look at the prstat -m information for your process; it will
let you know precisely where its time is being spent. (the results are not
decayed)
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
x */
return (NULL);
}
> int main()
> {
> int ii;
> pthread_t tid[3];
> pthread_setcanceltype(PTHREAD_CANCEL_ASYNCHRONOUS, NULL);
Again, you *really* don't want to do this.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
/opt/onbld/bin/i386/cw -_cc -xO3 -xarch=amd64
>
> /opt/SUNWspro/SOS10/bin/cc -xO3 -xarch=amd64
>
> debug:
> debug: file=/opt/SUNWspro/SOS10/prod/lib/amd64/values-xa.o [ ET_REL ]
> debug:
Isn't this:
6359912 /usr/lib/values-(star).o files s
ould imply a "Minor" release; 5.10 is Solaris 10, and 5.11 will
(presumably; marketing has futzed with this before) be Solaris 11.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Mon, May 15, 2006 at 03:33:43PM -0700, Jonathan Adams wrote:
> On Tue, May 16, 2006 at 12:00:32AM +0200, Roland Mainz wrote:
> >
> > Hi!
> >
> >
> >
> > This is slightly offtopic but due lack of a better list for this I am
> > asking this
On Tue, May 16, 2006 at 12:38:05AM +0200, Joerg Schilling wrote:
> Jonathan Adams <[EMAIL PROTECTED]> wrote:
>
> > you might avoid *some* of the expense (since, as of Solaris 10, system()
> > uses vfork(), even on multi-threaded processes. So the "duplicating
>
nce, as of Solaris 10, system()
uses vfork(), even on multi-threaded processes. So the "duplicating
the address space just to tear it down at exec() time" cost is gone.
On the other hand, you're still stopping all of the threads in the process
until the forked thread reaches exe
(dp == ¬able) {
printf(
"Manufacturer is unknown because of the orange forum embargo.\n"
"As the orange forum likes to get money for recent information,\n"
"it may be that this media does not use illegal manufacturer coding.\n");
}
and still be cstyle-compliant.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
PROTECTED] (work) Blog: http://schily.blogspot.com/
> URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Fri, Mar 24, 2006 at 12:59:46AM +0100, Roland Mainz wrote:
> Eric Lowe wrote:
> > TANSTAAFL.
>
> "TANSTAAFL" = ?
http://www.jargon.net/jargonfile/t/TANSTAAFL.html
There Ain't No Such Thing As A Free Lunch.
Cheers,
- jonathan
--
Jonathan Ada
ome amount of filesystem muckings-around; the
fact that the minimum unit of modification octupled causes any number of
performance and implementation headaches. Let alone assumptions about
filesystem blocksize and PAGESIZE being close to each other.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
rrible portability issue and people rarely use #ifdef
> to protect these statements correctly. Is there someone at Sun who's
> interested to discuss solutions and carry them forth to the ISO-C
> working group ?
As an aside, note that dtrace's D (which can pr
ump the acpi tables).
6230033 prtdiag should be implemented for Solaris x86
6313638 SMBIOS Support for Solaris
both integrated in snv_23, and both should be available in Solaris
10 Update 2.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
max_ncpu * ERPT_DATA_SZ)
These are for fatal events, possibly on multiple CPUs.
> And they are all preallocated? Sounds like a bug to me.
Well, if max_ncpus was just properly set to the actual maximum, as Andrei's
follow-on is done correctly, they wouldn't be allocating all this
extra spa
ch smaller.
>
> So what exactly uses this 256KB per CPU?
kmem cpu caches are about 20k/cpu (64 bytes/cpu/cache * ~300 caches * max_ncpu)
FMA looks like it's about 100k/cpu (ERPT_MAX_ERRS * max_ncpu * ERPT_DATA_SZ)
Cheers,
- jonathan
> Casper
> _
the text segment.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
de chapter on libumem out for comment.
The project is intended to be on-going.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
(or greater) atomic.h patch
as well as in Solaris Express / OpenSolaris.
Cheers,
- jonathan
> Rama
> This message posted from opensolaris.org
> _______
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
--
Jonath
s/ors/ands of 16-64 byte
quantities. Update 1 has the full range, including CAS.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
/access time updates; those are asynchronous, and would
have to happen for both ufs and vxfs.
> while metadata is updated only for each extent written for vxfs.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discu
ple feel it would be useful (in whatever context --
> inside or outside Sun).
And you could mark them "Fix Failed" if they got backed out. I personally
think this would be a good thing to do.
- jonathan
--
Jonathan Adams, Solaris Kernel Development
rt needed for ZFS
> just putback on friday.
There's still a pile of other work that needs to be completed before ZFS-root
is ready for prime time.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
you have to do complicated 64k-page-to-8k-page emulation logic for
those "legacy" apps.
In the end, the increase in complexity outweighed the benefits, and the
project was put aside. (I wasn't on the project, but I did have some
interactions with the project team
_______
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
usage (there's a maximum wastage
of the size of the snapshot).
It's very useful when you want a lot of mostly similar filesystems.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
artition table.
>
> And another quick question:
> I want to mount partitions from old Solaris on startup of system, not to type
> every time
> #mount /dev/dsk/c0d0s0 /export/home2
> Where should I add this filesystem so it would be mounted on every
> startup?/etc/mntta
d into Solaris.
(That's one of the side-effects of cpiotranslate, which fixes up the
owner/group data to match the packages -- it also removes files that aren't
in any package)
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
nderstanding is that that is the desired end functionality; currently,
you can't do it.
> First impressions are that ZFS is excellent and I am looking forward
> to trying more and more of the features later on, congratulations to
> eve
ed end functionality; currently,
you can't do it.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
On Tue, Nov 15, 2005 at 08:06:06PM -0500, Dennis Clarke wrote:
> On 11/15/05, Jonathan Adams <[EMAIL PROTECTED]> wrote:
> > On Tue, Nov 15, 2005 at 04:49:31PM -0500, Dennis Clarke wrote:
> > > On 11/15/05, Sean Wilcox <[EMAIL PROTECTED]> wrote:
> > > >
sure that's supported.
You could try to write-lock it using "lockfs -fw /", but I'm not sure
that's well-advised.
Cheers,
- jonathan
--
Jonathan Adams, Solaris Kernel Development
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
to observe the state of a cache, ie to
> determine the current number of unconstructed/constructed/allocated
> buffers?
There's no programmatic interface to do so, but the mdb(1) dcmds can give
some of that information (allocated/total; unconstructed v.s. constructed is
not calle
overly long post, but these umem facilities seem
> pretty powerfull of used correctly. As far as I can tell right now,
> it is unclear exactly how to do so.
Not a problem; if you have any suggestions on how to make the manpage more
clear, I'll be happy to get it changed.
Cheers,
39 matches
Mail list logo
